Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2005 Instance Expand / Collapse
Author
Message
Posted Tuesday, February 19, 2008 2:19 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 2, 2013 3:11 AM
Points: 7, Visits: 50
Hi
I want to remove an existing Database Instance from sql server 2005 installation server.
Already a separate production instance is running in the same server.
Without disturbing the production instance I need to do it.
Please suggests how to do it.

biju
Post #457255
Posted Tuesday, February 19, 2008 2:22 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, August 1, 2014 6:18 AM
Points: 1,618, Visits: 20,980
As usual go to Add/Remove programs and Remove SQL Server. In the un-installation screen select the Instance that you want to remove.

Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
Post #457257
Posted Tuesday, February 19, 2008 11:59 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, July 21, 2014 5:05 PM
Points: 2,644, Visits: 824
Just watch out for removing things like Management Tools. I removed an instance (think it was 2000, not 2005) on a multi-instance server and was left with the other SQL instance but no tools on the server to manage it.





Scott Duncan

MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
Post #457569
Posted Tuesday, February 19, 2008 5:19 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 2, 2013 3:11 AM
Points: 7, Visits: 50
Hi Pradeep,
As i had already mentioned there is also a another instance which is now in production.
Is the suggested method is the safer one?
If yes then what are the things I have to take care while removing the second database instance.
Post #457727
Posted Wednesday, February 20, 2008 12:53 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Saturday, August 16, 2014 5:48 AM
Points: 1,862, Visits: 3,602
biju127 (2/19/2008)
Hi Pradeep,
As i had already mentioned there is also a another instance which is now in production.
Is the suggested method is the safer one?
If yes then what are the things I have to take care while removing the second database instance.


Make sure you do not uninstall the client tools. Also make sure you specify the correct instance name to uninstall. Then you will be fine.

After uninstalling, go to your Windows Explorer and delete all folders (installation, data files) of the uninstalled instance.

I would suggest that you reboot your machine, once all this is done.


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #457850
Posted Friday, May 1, 2009 11:15 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, April 22, 2014 11:34 AM
Points: 49, Visits: 175
This is just a validation of the anxiety one might feel in using the wizard for removing an instance.

The problem is: the language used in the wizard screens AFTER choosing the instance to be removed seems to imply a GLOBAL rather than limited change and it nowhere again indicates which instance you are going to affect by proceeding.

When one is working on a production machine in which other instances are active, this is very disconcerting.




Post #708610
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse