Funny to read this. Why do you need this? Roll back planning for 15->16 upgrade? If yes, depending on how you upgrade, your downgrade options may be either syncing using rep server (atomic/non-atomic/direct load options - each with their own reservations - the major being it is just too slow to work for large data sets) or old good BCP utility (mark that per-partition BCP in will require you to drop clustered indices first - bad stuff). I've found that BCP-ing data is the most time-effective method (and the only method where you control how the things are done). RS "in-theory" may do things with 0 downtime (if you have applications already running on ASE 16 and you need to roll back due to stability issues, say). In practice - it will take ages for RS to sync back and chances are the Q will explode. For some reason, RS materializes data serially - and cannot load data in using either named pipes or parallel load for a single table (even with bulk option turned on).
Ergo - DDLGEN + BCP are your tools. Never actually used sybmigrate - wonder if this one is more time-effective. If you test this out - please update.
Cheers.
ps. Wonder if SAP tools (SUM DMO &c) will be at any stage released to do stuff like this. SAP engineers put loads of time writing this stuff to migrate from anyDB to anyDB - would have been nice to have them available too (daydreaming again). Probably not - too NetWeaver tied...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.