110 likes | 510 Views
UniData to SQL Conversion. Don’t lose your Informer investment…. PRESENTER: Tim Nicholson | Director of Customer Services, Entrinsik | March 6, 2012. Problem. Datatel clients are migrating from UniData to SQL Large investment in Informer reports
E N D
UniData to SQL Conversion Don’t lose your Informer investment… PRESENTER: Tim Nicholson | Director of Customer Services, Entrinsik| March 6, 2012
Problem Datatel clients are migrating from UniData to SQL Large investment in Informer reports Unidata is to SQL what oil is to water • Different structure • Different query language
Solution Write a toolthat migrates as much of the mapping and report metadata as possible.
Challenges Multivalues Computed Columns / I-Descriptors
Multivalues UniData SQL PERSON PERSON PERSON_ID FIRST_NAME LAST_NAME @ID FIRST.NAME LAST.NAME PERSON_LS PERSON_ID POS WHERE_USED WHERE.USED PEOPLE_EMAIL PERSON_ID POS PERSON_EMAIL_ADDRESSES PERSON_EMAIL_TYPES PERSON.EMAIL.ADDRESSES PERSON.EMAIL.TYPES
Computed Columns/I-Descriptors Become T-SQL functions Not associated with a table Take primary key as parameter Once mapped, treat like any other property Available in 4.3 Can use in SQL Block (4.2.8) as well
Limitations Cannot convert • TCL/ECL • Select/Returning • Remote links
Informer on SQL So what’s different? • Links • Any common value • Criteria Types • Simple, compound, Where clause • No Savelist • No Normalization
Informer on SQL So what’s different? • Data is normalized