April 20, 2015 at 9:52 am
Hi Folks,
I'm preparing a checklist for myself before getting ready to migrate from 2005 to 2012. Our largest database is a nice one at over 250GB. As you can guess it's also our most active and mission critical database. I'm thinking my best bet to minimize any downtime would be to Restore the DB (NORECOVERY) on the new server and keep rolling it forward with the transactional logs. Eventually I'll need to bring the old DB offline and do one last backup and apply that one to the new server but that should be a small time frame given the whole process could take several hours.
Just looking for any feedback/advice/gotcha's from people might have gone through this process.
Thanks,
April 20, 2015 at 10:03 am
yb751 (4/20/2015)
I'm thinking my best bet to minimize any downtime would be to Restore the DB (NORECOVERY) on the new server and keep rolling it forward with the transactional logs.
That should work very well.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 20, 2015 at 10:44 am
How about setting up log shipping and run the scripts for the backup and restore of the last T-Log in the time of cut-over.
April 20, 2015 at 11:54 am
udaynov17 (4/20/2015)
How about setting up log shipping and run the scripts for the backup and restore of the last T-Log in the time of cut-over.
This would probably work also but I'm not sure it's something I'd like to setup for a one time use.
April 20, 2015 at 12:03 pm
I used DBMirroring (SQL2005 and SQL2008), and it works nice! Migrated 500+ GB databases that way in seconds (assuming you have decent network and both are in the same LAN)
You can also restore with no recovery, as mentioned, then the day of the migration take most recent Tlog backup and restore on the target.
Tip
Check for orphaned SIDs. You need to reset those if you moved to a different SQL instance and you use SQL logins.
April 20, 2015 at 12:40 pm
sql-lover (4/20/2015)
TipCheck for orphaned SIDs. You need to reset those if you moved to a different SQL instance and you use SQL logins.
You're right about that one...I've been stung by this one before. :pinch:
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply