February 12, 2014 at 3:46 pm
1) Some of our user DB's vary in Recovery Model, either Full or Simple. Is there anything to consider for the migration?
2) I foresee a significant delay between initial restore/testing and final cutover (while we upgrade our DTS packages...manually!!) However, currently the DB's are backed up fully on a regular basis - any recommendations on the best way to synch them (bearing in mind Recovery Models above?)
Here's a rough plan I made...
Ok, does this preserve the continuity of the LSN's and synch up ? ....
Friday
8pm Place all DB's in Full recovery, kick off Backups (full);
8.01 Disable t/log backup job;
10pm Backups complete;
10.01 Commence zip/copy of .bak files;
10.02 Enable t/log backup job;
10.03 Run batch process to copy all subsequent log backups to new server;
10.04 Go to the bar, chug down a few beers;
Monday
9am Restore scripted logins onto target;
10am Restore full backups onto target;
3pm Restore scripted jobs onto target;
Tu/We/Th
Rebuild DTS packages in SSIS, test jobs etc...
Friday
5pm Reset all DB's on old server to Read only;
5.01 Restore all t/log backups (dozens, possibly hundreds by this point) at target, With NoRecovery, until the last one.
February 12, 2014 at 4:06 pm
You can still use DTS on 2008 if you want to have more time for migration. You can migrate DTS to SSIS in a phase 2.
February 12, 2014 at 4:30 pm
Hi Luis,
I think we've pretty much set our minds to getting this migration done, especially the DTS-SSIS conversion.
What about the rest? Do you agree with the step sequence/contents?
February 12, 2014 at 4:45 pm
That will work.
But why not apply those transaction log backups to the target as the backup occurs? You could logship those databases and keep them in sync and then the final cutover requires one last log backup and setting the original databases to read only. This method would save you significant time the night of the final cutover.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 13, 2014 at 2:48 am
SQLRNNR (2/12/2014)
That will work.But why not apply those transaction log backups to the target as the backup occurs? You could logship those databases and keep them in sync and then the final cutover requires one last log backup and setting the original databases to read only. This method would save you significant time the night of the final cutover.
Nahhh, that won't work.
It would leave the DB's on the target in Read-Only mode, thus defeating our objective to create/run packages that will write data to the DB's.
February 13, 2014 at 3:56 am
Come to think of it, after we have created our packages, is there any way to put the DB back into a state where we can restore any logs created at the original server?
February 13, 2014 at 6:26 am
Jake Shelton (2/13/2014)
SQLRNNR (2/12/2014)
That will work.But why not apply those transaction log backups to the target as the backup occurs? You could logship those databases and keep them in sync and then the final cutover requires one last log backup and setting the original databases to read only. This method would save you significant time the night of the final cutover.
Nahhh, that won't work.
It would leave the DB's on the target in Read-Only mode, thus defeating our objective to create/run packages that will write data to the DB's.
Yes it would work. Logshipping is just the preparation work and could be done days or weeks in advance.
Once you are ready, you only need to restore the final tlogs and bring the db fully online (and writable).
February 13, 2014 at 6:29 am
I find it extremely strange that a migration should be estimated to take a week. With enough preparation you could have this done less than a day.
I have completed several hundred migrations, with DTS, SSIS and very large dbs and none of them have taken longer than 4 hours.
February 13, 2014 at 6:30 am
Luis Cazares (2/12/2014)
You can still use DTS on 2008 if you want to have more time for migration. You can migrate DTS to SSIS in a phase 2.
This is correct and I would seriously consider this.
February 13, 2014 at 8:06 am
MysteryJimbo (2/13/2014)
I find it extremely strange that a migration should be estimated to take a week. With enough preparation you could have this done less than a day.I have completed several hundred migrations, with DTS, SSIS and very large dbs and none of them have taken longer than 4 hours.
We have almost a couple of hundred packages that need to be converted, albeit not too complex (2 connections and 2-3 steps). I have anticipated it'll take considerably longer than my example. I'd be curious to know how to accelerate the process.
February 17, 2014 at 8:30 am
MysteryJimbo (2/13/2014)
Jake Shelton (2/13/2014)
SQLRNNR (2/12/2014)
That will work.But why not apply those transaction log backups to the target as the backup occurs? You could logship those databases and keep them in sync and then the final cutover requires one last log backup and setting the original databases to read only. This method would save you significant time the night of the final cutover.
Nahhh, that won't work.
It would leave the DB's on the target in Read-Only mode, thus defeating our objective to create/run packages that will write data to the DB's.
Yes it would work. Logshipping is just the preparation work and could be done days or weeks in advance.
Once you are ready, you only need to restore the final tlogs and bring the db fully online (and writable).
I have had clients use this method numerous times to do migrations.
But are you saying that you need the databases on the target to be RW and the databases on the source to also be RW? Once the cutover is complete, then the target databases would be RW in the logshipping scenario.
But it both databases need to be RW at the same time, then you would have to do the restores of the logs and full backups at the same time.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 17, 2014 at 8:35 am
Jake Shelton (2/13/2014)
MysteryJimbo (2/13/2014)
I find it extremely strange that a migration should be estimated to take a week. With enough preparation you could have this done less than a day.I have completed several hundred migrations, with DTS, SSIS and very large dbs and none of them have taken longer than 4 hours.
We have almost a couple of hundred packages that need to be converted, albeit not too complex (2 connections and 2-3 steps). I have anticipated it'll take considerably longer than my example. I'd be curious to know how to accelerate the process.
That may be true, but DTS to SSIS migration can and should (IMO) be treated as separate migrations to the SQL engine itself.
You can leave the existing DTS migrations as a project which can be tackled in smaller, bitesize chunks and means the SQL Server and related processes are available within hours and not days. The existing DTS packages can be left running against the newly upgraded SQL Server (you may have to change internal connection strings).
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply