Named Instances
-
Currently I have a SQL 2000 Server Running Called Germanshepherd. I am currently configuring a new box with SQL 2005 to take the place of old Germanshepherd.
Since I can not have the same Server name on the network I Chose to call the New Server "NewBox" with an instance of SQL Server Called "GermanShepherd".
When I look up the new server I See "NewBox\Germanshepherd"
When I look up the old Box I connect with just "Germanshepherd"
When I get all the data and the packages I will change the machine name to Germanshepherd from NewBox. Will My Server path then be "Germanshepherd" or "Germanshepherd\Germanshepherd"? If it is the second this will not work since I have many ODBC's that are looking for Germanshepherd. how can I take care of this. Any info would be great.
-
Your old SQL 2000 installation was using a default instance, hence you could just connect with the computer name (GermanShepherd).
But you installed your 2005 as an instance - thus you will always need to connect to it using [MACHINE]\GermanShepherd...
Reinstall SQL 2005 on your new box as a default instance... Then when you rename the newBox to germanshepherd all should be swell...
-
Wow that is a real bummer. Since it is the Default instance I will need to take the old machine down and bring the New SQL Server up.
That is very risky if something goes wrong. I wish there was a better way. -
What Ian means is.
UnInstall SQL2005 on the 'NewBox'.
ReInstall SQL2005 on the 'NewBox' as the 'Default Instance' (Don't give it the Instance name of 'Germansheperd').
Test by connecting to 'NewBox' instead of 'Germanshepherd'.
When you are happy re-name the server from 'NewBox' to 'Germanshepherd' (The old box should be shutdown before you do this).
If there is a problem in the last step you can rename the server back, and start the original box so that everything is still running.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply