|
Knowing that everyone's experience may be a bit different, I'm asking for advice on the best way to migrate my v16 database to v17. My v17 software is on a shiny new windows 2016 VM, and the database in question is about 50GB. The textbook answer seems to be to copy the database to the new server, open it in v17, then do an unload/reload. I tried that over the weekend, using the command line DBUNLOAD. No errors, but in the reload.sql file that was created, all the users (including DBA) had a blank password. One option might be to do an unload on the v16 server, copy the data files over, then re-load on the v17 machine (drive letters are all the same). Not sure if there's an advantage to that, though. |
If that is a problem "DBUNLOAD -up" is your friend - or the dbunload variants that do an automatic reload like -ac, -an, -ar...:) That being said, I would always recommend to use the new version's DBUNLOAD if feasible to do the unload, not that of the old version. 1
'"DBUNLOAD -up" is your friend' Embarrassing. This is what I get for not reading all the way to the end of the documentation. Thanks
(14 Oct '19, 13:50)
Bud Durland MRP
|