SQL Server, convert a named instance to default instance?

Question

I need to convert a named instance of SQL server 2005, to a default instance.

Is there a way to do this without a reinstall?

Answer 1

AFAIK no, one reason is the folder structure on the hard drive, they will have a name like MSSQL10.[instancename]

Answer 2

The only way to change the instance name is to re-install - uninstall and install as default instance.

Answer 3

You shouldn't ever really need to do this. Most software that claims to require the default instance (like Great Plains or Dynamics) doesn't actually.

If you repost with your situation (installed X, then Y, but need to accomplish Z) I bet you'll get some good workarounds.

Answer 4

The problem is, 2 out of 6 of the developers, installed with a named instance. So its becoming a pain changing connection strings for the other 4 of us. I am looking for the path of least resistance to getting these 2 back on to our teams standard setup.

Each has expressed that this is going to be, too much trouble and that it will take away from their development time. I assumed that it would take some time to resolve, in the best interest of all involved, I tried combing through configuration apps installed and didn't see anything, so I figured someone with more knowledge of the inner workings would be here.

Answer 5

A lot of times I'll use client alias to point an application at a different sql server than the ones it's connection string is for, esp. handy when working on DTS or an application with a hard coded connection string. Have everybody use a commonly named alias, use the alias in the connection string and point the alias’s on each dev box to the to the different instances. That way you won't have to worry about if the server is the default instance or not.

Answer 6

@ChanChan

This is why a lot of companies store their applications' connection strings at the machine level instead of the application level.

Just take the connection string out of the source code entirely. Then have everyone put their connection string in their machine.config.

This has the added benefit of avoiding unnecessary app-specific environment logic, i.e. when you copy your application to the staging server, the staging server already "knows" what database to use.

Hope this helps.

Answer 7

Followup question (an example why I need to do it)...

I'm migrating data from SQL Server to Oracle in the Oracle tools (Oracle SQL Developer), but Oracle doesn't seem to support the "\" character used to separate the server \ instance in the name in their connection tool (the tool has a special dialog for connecting to SQL Server).

Seems bad that you must reinstall SQL Server to change the instance name to "MSSQLServer" (which is the default instance name).