Migration from Paradox to Sybase
ARW
I am currently running an EXTREMELY overworked Paradox 7.0 database, and
have watched the support for this database dwindle away to nothing,
while Corel plans on making it more (a quote from Comdex "Access-like")
My usage needs are quickly increasing, and SQL seems to be the best
solution. I would like to hear from anyone who has made a similar
migration to SQL (or anything else for that matter) and what I need
to keep an eye out for. I know that Im going to have many issues pop up
unexpectedly, and I'd like to see what others have gone through in a
relational to SQL based DB configuration move.
Post here, or email me at awa...@idtdna.com
Thanks in advance.
Aaron R. Warner
Chief Information Officer
Integrated DNA Technologies, Inc.
awa...@idtdna.com
<http://www.idtdna.com>
Ewan Grantham
>> My usage needs are quickly increasing, and SQL seems to be the best
solution. I would like to hear from anyone who has made a similar
migration to SQL<<
Have just been working on such a situation for my current client. Their
conversion is complicated by the fact that the Paradox system will
continue to get data for a while, so the conversion has to be able to be
run on a weekly basis, and to determine what needs to be converted and
what not.
FWIW, I chose to go with a three-step approach. I have an Access 97 DB
that sucks in the Paradox data. It then has several macros and queries
that do the adjustments and key conversions, and then exports flat files
which get FTP'd up to the Sybase UNIX box. There the data is bcp'd in, a
couple stored procs run as a final sanity check, and then the data is
put into the live Sybase database.
Hope this helps,
Ewan
--
Ewan Grantham 74123...@compuserve.con
12/10/96 11:15
---------
Using: OUI PRO 1.5.0.2 from http://www.dvorak.com