Solved

Upgrade of MS SQL instance from 2005 to 2008 r2 failed

Posted on 2011-03-03
7
625 Views
Last Modified: 2012-06-21
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.
0
Comment
Question by:StammHD
  • 3
  • 3
7 Comments
 
LVL 13

Expert Comment

by:geek_vj
ID: 35033827
Modifying registry entries may corrupt the exisiting setup. So, before modifying/deleting anything, ensure that you take a complete backup of the registry. Also, ensure that you have the current backups of all databases (including system dbs) and placed at a secure location (preferably on a different server).
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!
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35034218
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
0
 

Author Comment

by:StammHD
ID: 35036142
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.
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 20

Expert Comment

by:Marten Rune
ID: 35037985
Sounds like a plan. Good luck!

//Marten
0
 

Accepted Solution

by:
StammHD earned 0 total points
ID: 35059693
in the end I had no luck.  I didn't have another server to test with and ended up doing this:

http://www.intellitechture.com/SQL-Server-2008-Install-Nightmare/?replytocom=228#respond

It's a sledgehammer, but it worked.  I was able to install after that.
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35061178
Thanks for sharing. Though one, I'll give you that!

//Mårten
0
 

Author Closing Comment

by:StammHD
ID: 35225413
Figured it out, included link for solution.  Manual uninstall of the incomplete SQL 2008 install
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Mssql SQL query 14 45
Filtered index 5 55
Help with SQL - TOP 10 by date and by group 13 32
Help with simplifying SQL 6 48
Long way back, we had to take help from third party tools in order to encrypt and decrypt data.  Gradually Microsoft understood the need for this feature and started to implement it by building functionality into SQL Server. Finally, with SQL 2008, …
Hi all, It is important and often overlooked to understand “Database properties”. Often we see questions about "log files" or "where is the database" and one of the easiest ways to get general information about your database is to use “Database p…
A short film showing how OnPage and Connectwise integration works.
This is a video that shows how the OnPage alerts system integrates into ConnectWise, how a trigger is set, how a page is sent via the trigger, and how the SENT, DELIVERED, READ & REPLIED receipts get entered into the internal tab of the ConnectWise …

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now