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