Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Migrating from 2K to 2K8 - a few questions


Migrating from 2K to 2K8 - a few questions

Author
Message
Jake Shelton
Jake Shelton
SSC-Enthusiastic
SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)

Group: General Forum Members
Points: 181 Visits: 916
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.
Luis Cazares
Luis Cazares
SSCrazy Eights
SSCrazy Eights (8.6K reputation)SSCrazy Eights (8.6K reputation)SSCrazy Eights (8.6K reputation)SSCrazy Eights (8.6K reputation)SSCrazy Eights (8.6K reputation)SSCrazy Eights (8.6K reputation)SSCrazy Eights (8.6K reputation)SSCrazy Eights (8.6K reputation)

Group: General Forum Members
Points: 8556 Visits: 18143
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.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?


How to post data/code on a forum to get the best help: Option 1 / Option 2
Jake Shelton
Jake Shelton
SSC-Enthusiastic
SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)

Group: General Forum Members
Points: 181 Visits: 916
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?
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21091 Visits: 18259
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

Jake Shelton
Jake Shelton
SSC-Enthusiastic
SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)

Group: General Forum Members
Points: 181 Visits: 916
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.
Jake Shelton
Jake Shelton
SSC-Enthusiastic
SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)

Group: General Forum Members
Points: 181 Visits: 916
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?
MysteryJimbo
MysteryJimbo
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1348 Visits: 15327
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).
MysteryJimbo
MysteryJimbo
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1348 Visits: 15327
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.
MysteryJimbo
MysteryJimbo
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1348 Visits: 15327
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.
Jake Shelton
Jake Shelton
SSC-Enthusiastic
SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)SSC-Enthusiastic (181 reputation)

Group: General Forum Members
Points: 181 Visits: 916
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search