This is a question dealing with the differences of a relaod.sql script used to upgrade a SQL Remote database in contrast to re-extract a SQL Remote database.
A verbose introduction (DBEXPLAIN -v):
We are about to migrate our SQL Remote databases from ASA 8.0.3 to SA 12.0.0 and are just planning the customized unload/reload process. Our goal is to build a small tool that does this migration automatically, i.e. without having to re-extract remotes.
So we want to handle the migration similar to our custom extraction, i.e. would build a tool that does unload the data and uses a parametrized reload script to build the database.
These two tasks (extraction vs. migration of a remote database) seem quite similar with the following differences:
So my question is:
Can I use basically the same parametrized reload.sql script I use to re-extract when I assure these two differences get handled accordingly?
This would include that I would not only parametrize the reload.sql script with obvious parameters like the remote user/file address and the GLOBAL_DATABASE_ID (as the re-extraction already does) but would also have to call sa_setremoteuser and sa_setsubscription with the according values taken from the v8 database. (Yes, I'm aware that these are undocumented functions but I'm sure they are built for this exact usage...)
If so, that would really smooth:)
Or do I have forgotten something relevant?
[This is not a complete answer, just my test results so far. Handle with care...]
Besides the schema and the data from user tables, the following topics seem to need particular care (and will be handled correctly by using DBUNLOAD -ar, of course):
Feel free to comment, correct, add, whatever:)
answered 22 Sep '10, 21:00