Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server 2005 Instance


SQL Server 2005 Instance

Author
Message
biju127
biju127
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
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
Adiga
Adiga
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1636 Visits: 21012
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
thecosmictrickster@gmail.com
thecosmictrickster@gmail.com
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3336 Visits: 932
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

biju127
biju127
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
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.
Marios Philippopoulos
Marios Philippopoulos
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1958 Visits: 3741
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.

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
Scott MacCready
Scott MacCready
SSC Rookie
SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)

Group: General Forum Members
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.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search