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 Monday, February 17, 2014 8:30 AM


SSC-Insane

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

Group: General Forum Members
Last Login: Today @ 9:16 AM
Points: 20,465, Visits: 14,095
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


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 #1542160
Posted Monday, February 17, 2014 8:35 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, April 16, 2014 2:08 AM
Points: 1,350, Visits: 15,200
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).
Post #1542166
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse