Re: Make SQL Server 2005 the Default instance when SQL 2000 was installed first

The only way to rename an instance is to uninstall and reinstall the
instance. You can only have one default instance of SQL (any version) on a
system. So, the short answer is no. On the other hand, there is no
functional difference between the default instance and a named instance.
The only differences is that the default instance gets port 1433, unless you
force a change, and it has a single-part name. On multi-instance systems,
partucularly clusters, I only use named instances so all the servers look
the same on the net. If you are using JDBC or a simlar connecter that needs
to attach to a specific port, you can use the SQL Configuration Manager
tool to assign a permanent port to the named instance.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




"John Kotuby" <johnk@xxxxxxxxxxxxx> wrote in message
news:uxMxjV3AHHA.992@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I am getting a tough lesson in remote Web Server administration. We had
asked the hosting company to install SQL Server 2005 Standard on our
dedicated Windows 2003 ENT Web server when they built it from scratch.
Unfortunately communications between Sales and Tech failed, such that they
installed MSDE (2000) as the default instance of SQL Server. When they
realized their mistake they installed SQL Server 2005 STD as a named
instance (MSSQLSERVER2).

I do not have access to the install media and therefore cannot uninstall
and reinstall everything remotely via Remote Desktop. In fact, what is
more disturbing is that I can't even find MSDE in the Add/Remove programs
list. SQL Server Management Studio clearly shows the default instance as
MSDE.

The Hosting company is dragging their heels and wants to charge more setup
fees. Is there any way that I can make SQL Server 2005 the default
instance without uninstalling all instances of SQL Server and then
re-installing? I can't seem to find documentation about that.

Thanks in advance for any suggestions....



.

Relevant Pages

  • Re: HOW DO I REMOVE AN UNUSED SQL SERVER 2005 INSTANCE?
    ... I haven't seen a how-to on a manual uninstall for SQL 2005. ... Microsoft SQL Server MVP ... defunct local owner to a domain owner (assuming if the service was owned ...
    (microsoft.public.sqlserver.setup)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Starting ms sql server 2008 express
    ... I decided to try to uninstall and reinstall but found that simply ... SQL Server 2005 Express Edition. ... there is a previous install. ...
    (comp.databases.ms-sqlserver)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)