I'm doing a pilot project to see what effort would be required to move our SQL Anywhere 9 database to version 12. I'm wondering what the proper approach would be to accomplish this. In Sybase Central for SQL Anywhere 12, I unloaded the v9 database and then loaded it into a new v12 database. It finished without producing any errors so does this mean it was a clean migration??? Thanks, asked 27 Feb '12, 10:07 Bwery |
That should be the correct procedure according to the documentation. If there were no errors, then nothing was noticeably wrong with your upgrade from the perspective of the database server and all of the tables, procedures, data, etc... should have been migrated. The static structure of your database should have been restored. Note that it is always prudent to heavily test your application after such a significant change before placing it into a production environment. It's always a possibility that something was missed or that some behaviour change (intended or otherwise) has broken the run-time behaviour of your database. answered 27 Feb '12, 10:39 Phil Mitchell 1
Therefore I would highly recommend the docs, particularly the bunch of "behavior changes" pages. Besides that, you usually would like to know not only about things that do not work anymore (or different than before) but also check how you will take advantage of new features...
(27 Feb '12, 10:48)
Volker Barth
Replies hidden
I agree that you should read the "Behavior Changes" sections. The database migration worked, but will your application work?
(27 Feb '12, 14:01)
Breck Carter
Yes, full system testing will have to be performed to make sure that everything still works. I wanted to make sure that "step 1" was done right. Thanks everyone.
(27 Feb '12, 14:20)
Bwery
|
In our migration we found that synch scripts didn't work the same. answered 28 Feb '12, 10:44 Eric Hofer |