August 10, 2011 at 2:22 pm
I need to upgrade from SQL2k5 Std. to SQL2k8 Ent.
I've seen this article that describes some of the hassles, but it doesn't explain the Std. -> Ent. difference, nor if it can be done.
http://blogs.lessthandot.com/index.php/DataMgmt/DBAdmin/mirroring-sql-server-2005-to-sql-server-2008
I've been working through the process as though there isn't an issue in the Std. -> Ent. upgrade. I've encountered lots of issues working through the process, most were documented in the blog, but I was wondering if anyone has any experience doing this, because, just like the blogger - I have a boss with very little tolerance for down time.
August 10, 2011 at 2:30 pm
Create the new server from scratch with all sps and windows updates.
Test the process. Backup on 2k5, to a local drive (shared). Restore from 2k8. Du your due diligence that everything works fine there.
Then for the big day, restore the last full backup.
take a diff of 2k5 and restore that as well (both of those with norecovery).
I'd be paranoid here and run checkdb() if I have a few minutes to spare.
Then when you're really ready, take the tail backup on 2k5 (backup log with NORECEVORY, makes the db unavailable and no more changes can happen here, option be would then to put in in read only).
Then restore the tail log on 2k8 and point the apps to the new server. Total downtime should be minutes.
If something fails, just put the old db back to read_write and that keeps the downtime to a minimum.
August 11, 2011 at 6:16 am
Thanks. I hadn't thought of the NORECOVERY option, making the 2k5 database unavailable for updates.
August 11, 2011 at 6:33 am
BigSam (8/11/2011)
Thanks. I hadn't thought of the NORECOVERY option, making the 2k5 database unavailable for updates.
That's what we're here for :-).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply