Solved

How do I manually remove a failed SQL Server 2008 installation?

Posted on 2010-11-09
4
1,138 Views
Last Modified: 2012-08-13
After installing the first node of a SQL Server 2008 R2 failover cluster, our storage "support" team decided it would be a good idea to erase the disks upon which the SQL Server system disks resided. They were successful and rendered the installed node useless. The gui tools could not uninstall because Master was missing.  Does anyone know how to manually remove SQL Server so that it can be reinstalled
0
Comment
Question by:Integr8
  • 2
4 Comments
 
LVL 3

Expert Comment

by:adammet04
ID: 34098657
How about rebuilding the node completely? rather than just manually uninstall sql, could you rebuild the box itself?. might be a cleaner solution.
0
 
LVL 16

Expert Comment

by:EvilPostIt
ID: 34101642
Are you just missing the databases?

If so you could rebuild the master database and then maybe uninstall.

Here is an article which should guide you through rebuilding the system databases.
0
 

Accepted Solution

by:
Integr8 earned 0 total points
ID: 34207936
What ultimately worked was to keep uninstalling SQL Server until all of it was gone.  The windows node had 2 sql server failover nodes plus a default standalone instance and a named standalone instance running on it. By failing over the cluster instances to another node and running the install gui  until all of the standalones were gone, it was possible to remove all of SQL Server from the Windows node. It was necessary to reboot after each complete uninstall so that no error was generated on the next uninstall. All pieces of SQL Server on this server were SQL Server 2008 R2 Enterprise Edition.
0
 

Author Closing Comment

by:Integr8
ID: 34228752
I'm disappointed that I had to provide my own solution.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

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

I have written a PowerShell script to "walk" the security structure of each SQL instance to find:         Each Login (Windows or SQL)             * Its Server Roles             * Every database to which the login is mapped             * The associated "Database User" for this …
In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.

830 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