By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,853 Members | 995 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,853 IT Pros & Developers. It's quick & easy.

No longer need default instance of SQL Server

P: n/a
AJ
Currently I have a server that has two instances of SQL Server that are
both heavily used. We are moving the databases that are on the default
instance of this server to a new server. Since the old server will
only need one instance (the current named instance) of SQL Server is
there a good way to remove the default instance and make the named
instance the default? If this change is possible will the name of the
current named instance need to be changed? Will all of the programs
currently accessing the named instance need to change their connection
string?

Jul 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
AJ (ab********@mnlife.com) writes:
Currently I have a server that has two instances of SQL Server that are
both heavily used. We are moving the databases that are on the default
instance of this server to a new server. Since the old server will
only need one instance (the current named instance) of SQL Server is
there a good way to remove the default instance and make the named
instance the default? If this change is possible will the name of the
current named instance need to be changed? Will all of the programs
currently accessing the named instance need to change their connection
string?


You could uninstall the default instance and keep the named instance
as it is. To be honest, I have not actually tried it, but I am quite
convinced that it is possible.

I don't see the point with making the named instance the default
instance, not the least if you would have to go and change
connection strings.

And I don't think there is a simple way to rename an instance. Probably
the easiest method would be to detach the databases, and attach them
to the existing default instance. If you really want to have them a
default instance, that is.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #2

P: n/a
AJ
Thanks for your suggestion. I guess I just thought there had to be a
default instance. In a test environment I created a default and a
named instance and then removed the default instance and everthing
seemed to be fine. It seems this will be my solution.

AJ

Jul 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.