Default Local Instance Name

Question

Default Local Instance Name

Craig Fisher

Newbie

Points: 3
More actions
August 14, 2006 at 7:48 am

#113852

When first intalling SQL 2005, it appears that a named instance was used that looks like this --> MyServerName\MyServerName. A large and complex database was created and ODBC connections, many stored procedures, programs, many reports, etc. have been created all referencing this name MyServerName\MyServerName.
Now, trying to instal Microsoft Dynamics CRM package, it demands that the default local instance name be the same as the machine name. Since there does not appear to be a default local instance with the machine name (MyServerName), the CRM install fails.
How can I create a default local instance with the same name as the Machine without killing the existing database and all of its parts that referenece the MyServerName\MyServerName instance?
C

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Bill Galashan SSChasing Mays Points: 623 More actions · Answer 1

I would suggest installing a second instance as a default instance. Once you have this you should be able to detach all databases from the named instance and attach to the default instance if required or run with the two instances on the server.

If you detach and attach you will have connection problems where the connection string uses the named instance name.

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 2

Have you contacted MS to find out if there is a fix/workaround for installing on a named instance ?

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

colin.Leversuch-Roberts SSC Guru Points: 52643 More actions · Answer 3

sounds strange to me .. you can alias an instance to a non instance name - had to do this with some third party apps - this allows connectivity by instance and other names e.g. myserver/instance1 or Kodiak. You can also set the netname to be different - if your company insists on meaningless servernames with underscores for isntance you can set a more meaninigful net name to allow remote connections.

I would have thought your app would be happy with an instance but try aliasing.

[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/