Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Migrating from 2K to 2K8 - a few questions Expand / Collapse
Author
Message
Posted Wednesday, February 12, 2014 3:46 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, July 7, 2014 7:49 AM
Points: 163, Visits: 831
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.



Post #1540988
Posted Wednesday, February 12, 2014 4:06 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 3:38 PM
Points: 3,319, Visits: 7,168
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.


Luis C.
I am a great believer in luck, and I find the harder I work the more I have of it. Stephen Leacock

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1540991
Posted Wednesday, February 12, 2014 4:30 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, July 7, 2014 7:49 AM
Points: 163, Visits: 831
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?
Post #1540993
Posted Wednesday, February 12, 2014 4:45 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 2:28 PM
Points: 21,202, Visits: 14,887
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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1540994
Posted Thursday, February 13, 2014 2:48 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, July 7, 2014 7:49 AM
Points: 163, Visits: 831
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.
Post #1541076
Posted Thursday, February 13, 2014 3:56 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, July 7, 2014 7:49 AM
Points: 163, Visits: 831
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?
Post #1541099
Posted Thursday, February 13, 2014 6:26 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 7:33 AM
Points: 1,361, Visits: 15,264
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).
Post #1541150
Posted Thursday, February 13, 2014 6:29 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 7:33 AM
Points: 1,361, Visits: 15,264
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.
Post #1541151
Posted Thursday, February 13, 2014 6:30 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 7:33 AM
Points: 1,361, Visits: 15,264
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.
Post #1541153
Posted Thursday, February 13, 2014 8:06 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, July 7, 2014 7:49 AM
Points: 163, Visits: 831
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.
Post #1541218
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse