StammHD
asked on
Upgrade of MS SQL instance from 2005 to 2008 r2 failed
For one of my client a tech went on site to upgrade SQL and things didn't work the next day. After looking into it I had thought he had just installed SQL server 2008 R2, but not upgraded any instances or the Management Studio. So I fixed the management studio and upgraded that.
Then I ran SQL 2008 Express Edition with advanced Services again and choose to upgrade from 2005. The Rule Check failed on "Previous version"
After digging through forums and looking at other peoples similar issues there appear to be some registry keys. When I was looking into this I realized there is an entry for "MSSQL10_50.instance" and it shows the old 2005 database that it upgraded from etc. However this instance doesn't actually exist so I'm guess this is the failed previous upgrade. The original 2005 database is running and working.
I'm wondering if I can delete the entire Registry folder for teh failed instance and the directory with all the files for it and try again. Would that clear the failed previous upgrade? or would it cause complete Chaos of some kind I don't know.
Thanks in advance.
Then I ran SQL 2008 Express Edition with advanced Services again and choose to upgrade from 2005. The Rule Check failed on "Previous version"
After digging through forums and looking at other peoples similar issues there appear to be some registry keys. When I was looking into this I realized there is an entry for "MSSQL10_50.instance" and it shows the old 2005 database that it upgraded from etc. However this instance doesn't actually exist so I'm guess this is the failed previous upgrade. The original 2005 database is running and working.
I'm wondering if I can delete the entire Registry folder for teh failed instance and the directory with all the files for it and try again. Would that clear the failed previous upgrade? or would it cause complete Chaos of some kind I don't know.
Thanks in advance.
all abovbe is good advice! I agree with it all, but ...
I would like to suggest a different path!
Since you have a instance that has been acting bad I would suggest you to build another server, move the database there and do the inplace upgrade on that machine.
If it works out I would uninstall ALL versions of SQL on the server and do a clean install of 2008 R2. Then move the migrated database onto it. Ofcourse this means having control over database, user accounts (sp_helprevlogin), sql jobs, endpoints if exists, linked servers if exists or any server level objects.
A lot more work, but in the end it leaves you with a system that dont have any questionmarks attached to it! If need be (and this server is a sole sql server) I would actually reinstall it from OS and up!
Though my proposal is NOT fast, the benefit is that it leaves a system where no fast fixes has been aplied.
//Marten
I would like to suggest a different path!
Since you have a instance that has been acting bad I would suggest you to build another server, move the database there and do the inplace upgrade on that machine.
If it works out I would uninstall ALL versions of SQL on the server and do a clean install of 2008 R2. Then move the migrated database onto it. Ofcourse this means having control over database, user accounts (sp_helprevlogin), sql jobs, endpoints if exists, linked servers if exists or any server level objects.
A lot more work, but in the end it leaves you with a system that dont have any questionmarks attached to it! If need be (and this server is a sole sql server) I would actually reinstall it from OS and up!
Though my proposal is NOT fast, the benefit is that it leaves a system where no fast fixes has been aplied.
//Marten
ASKER
Thank I'm going to do a full back and try the fast way. If it goes bad I'll have the weekend to do it the long way. I'll let you both know. Thanks for the feedback.
Sounds like a plan. Good luck!
//Marten
//Marten
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks for sharing. Though one, I'll give you that!
//Mårten
//Mårten
ASKER
Figured it out, included link for solution. Manual uninstall of the incomplete SQL 2008 install
Once the above precautions are taken, you can proceed with the deleting of the registry keys. If you are deleting only the specific entries under MSSQL10_50.instance, then it only affects SQL Server running on the server.
By any chance, if you feel that after deleting the entries, SQL Server is not getting upgraded/not running properly, u can restore the registry to the previous state from the backup.
Hope this helps!