I have SQL 2005 SP4 installed on Win2k8. After I had it setup, we decided to change the name of the computer. In doing so, I think I might have broken something (possibly named pipes?) but I'm not sure as a) I'm not a DBA and b) I'm still in the process of setting this server up, so I can't say it was working before. And I really don't want to start over.
However, when I open up SSMS, the instance name shows the correct computer name, but under logins I have {OLDSERVERNAME}\SQLServer2005MSFTEUser${OLDSERVERNAME}$MSSQLSERVER and I think this is breaking my ability to do remote services connections.
So the question is, how to fix this?
There are considerations you need to be aware of for SQL when renaming the host machine. Do a
and see if it is returning the new machine name. If not, have a look through this MSDN article, follow the directions inside.
exec sp_dropserver 'Oldname' go exec sp_addserver 'Newname', 'local' go
Then go to the SQL Server Configuration Manager and restart the SQL Server (MSSQLSERVER) service.
All of the logins will keep the same name and should work fine. If you want to you can remove them and re-add them. They keep working because SQL uses SIDs to match those logins and groups to the host OS and these SIDs haven't changed. Only the display information is incorrect. The Named Piped protocal itself should be working fine.