June 22, 2012 at 4:09 am
I have SQLserver 2005, 2008 & 2008R2 on my Windows 7 machine. I tried to upgrade to 2012 but it failed because I didn't have 2008 R2 SP1. I tried using auto-update to instal SP1 - but it failed with an unknown error. So I downloaded 2008 R2 SP1 and tried an upgrade. It worked for the 2008, but not 2008R2 - "wait on the database engine recovery handle failed" [I've looked all over for a cure - but can't find one.
So I now have 2008 R2 and 2008 R2 SP1. I have databases under both but, unfortunately, do not have SA rights to the SP1 instance as it is linked to an application. So I have 2008 R2 SP0 databases I want to upgrade to 2012.
I need 2005 to be seen on the machine - even though not used, But I don't need 2008 or 2008R2. So I thought that I could backup my databases, install 2012, de-install 2008 & 2008 R2, restore the databases into 2012. Will that work?
Should I install a brand new 2008 R2 SP1 and move my databases across (backup/restore?) before deleting the 2008 R2 SP0 and then upgrading to 2012?
Any other ideas?
June 22, 2012 at 5:13 am
I really don't want to sound mean, but what a mess. Why do you have so many different instances all running on the same machine?
But, to answer your question, yes, a backup of a 2008 or 2008R2 database can be restored to 2012. That's actually a good way to do the upgrade. I prefer that approach because it lets me get the 2012 instance all configured while leaving the older instances alone (not so simple in your case).
Make sure you run the Upgrade Adviser (free from Microsoft) prior to starting the process.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 22, 2012 at 10:08 am
Thank you.
I agree that it is a mess - but 2005 and one of the 2008s were installed as part of application installs - they wouldn't let me add the database to my current 2008. That said - the application calling for a second 2008 does allow me to migrate the database to another instance and I will do that. As mentioned, the other application is happy for me to move the database but, on startup, it checks that 2005 is there even if it doesn't use it.
Back to 2012. Thanks for your advice. I will now back up the databases, install 2012, restore the databases into 2012 then delete 2008. It is annoying that the upgrade of one of the 2008 instances to R2 SP1 doesn't work. The internet seems to be full of similar issues - but, though I've tried a few, I've decided on installing 2012 as a separate instance.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply