Of course, there are TechNet/MSDN articles about just that but still we were cautious since while following the instructions, we soon bumped into this screen:
So we could click it and see what happened, but it didn’t feel right. It was a production SQL Server running another instance as well which wasn’t to be removed at all… So we could afford no risks here.
Gladly I ran my own test environment based on SSD. On my own SQL Server I added an another dedicated SQL Server instance (named Test), snapshotted the VM, removed the SQL Server instance and documented every single step of it. This posting is about just that.
Important to know is that the SQL Server instance which we had to remove didn’t host any SQL Database anymore besides the regular system databases.
Procedure
Before you start make sure there is a valid backup/snapshot/clone in place so you can go back when things go wrong!
- Log on to the SQL Server with an account which has local admin permissions;
- When it’s a virtual machine, make sure you connect through RDP based on session 0 (AKA physical console session);
- Make sure you’re the only one who is logged on to that SQL Server on that moment;
- Go to the Control Panel > Program and Features and select Microsoft SQL Server 2008 R2 (64-bit) > click on Uninstall/Change;
- Now this screen appears:
Select the option Remove - Setup Support Rules are installed/loaded now, just wait a moment;
- Just give it a couple more seconds (depending on the speed of your server);
- Now you can select the SQL Server instance to remove. Look at the dropdown box next to the option Instance to remove features from:
As you can see, both SQL Server instances are shown here. I select the SQL Server instance Test; - Only select the features which are SQL Server instance specific. So DON’T select the Shared Features like Management Tools and so on…
- Removal Rules are loaded now, be patient;
- Now a summary is shown about the steps you’re going to make. Until now you can go back without doing any harm at all. So READ this screen and at Step 9 MAKE SURE you’ve selected the CORRECT SQL Server instance.
When you’re 100% SURE all is OK hit Remove. Now you’ve entered the Point-of-No-Return… - After a while the in Step 9 selected SQL Server instance and it’s related Features are removed;
- Click Close and you’re done .
As you can see, the removal of SQL Server instance on a SQL Server running multiple SQL Server instances is a straight forward process. But like anything, prepare yourself, make a valid backup/snapshot/clone and know what you’re doing.
15 comments:
Thanks!
You saved my time!
Thank you very much. Very helpful.
hi should it be a problem if the service is stopped because i have a SQL that is stopped and i cannot remove it
hi should it be a problem if the service is stopped because i have a SQL that is stopped and i cannot remove it
Hi Malik.
I am not sure whether the state of the SQL Server service influences the removal of that same instance. What error do you get?
Cheers,
Marnix
thanks!
Thanks. That was very helpful.
thank you so much brother
I think is you need to go to SQl Server Configuration Manager and Stop the instance that you want to remove before doing.
Nice work bud. Saved me some valuable time.
Perfect and helpful post!
Thanks
Thanks for the timesaver!
Thanks you sir.
This was exactly what I needed, thanks so much!
Post a Comment