General discussion


SQL vs. UniData

By aileen.sandoval ·
Hi! I'm looking for some friendly, and honest advice. One of our application vendors recently announced an option to move to from a UniData environment to a SQL 2005 environment. However, the app itself is still UniData 6.x/PICK. A fellow customer advised that this was still a fairly unstable combination.

I don't have enough knowledge or experience to evaluate the implications on this. I'd appreciate any thoughts you might have.

St. Louis, MO.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -


by kumar24.soft In reply to SQL vs. UniData

We can use ODBC for mapping .At oracle you need to create some table that is related to ODBC fields of unidata table. ODBC is simple mapping procedure that we can use in any technologies. But in unidata here it depends on the table and data transfer rate of the intranet.

I could help you if you give me data transfer rate of your server.

Collapse -

Unidata Data Conversion

by LegacyDatabase In reply to SQL vs. UniData

This is an old thread but I'm sure other people have bumped into it because of Unidata. My advice is to stick to Unidata if you have a PICK program. It's simply too much work to have to bridge SQL to Unidata. Another option is to convert your legacy databse from Unidata to SQL completely, but this would mean that your app will need to be converted as well. Weigh the pros and cons of each environment based on your goals. Is the motivation to move to SQL driven by a need to mine the database 'easier'? If so, you may want to convert to SQL and off of PICK altogether. Just my two cents.


Related Discussions

Related Forums