The documentation says, you need to run those stored procs - although SQL Server 2000 is mentioned to be able to 'fix itself' - but the steps are still mentioned as mandatory.
Check this link:
http://www.sqlservercentral.com/columnists/bknight/renameserver.asp
Regards,
Vikram
Mentioned stored procedures update the server name in the system catalog. Otherwise you might have problems connecting to the instance from other machines. You may also need to use sp_addlinkedserver and sp_setnetname on other instances to reflect the name change.
One thing to note... that the books online doesn't tell you is that you have to stop and restart the sql server service for the change to take effect...
I renamed the machine (not the instance, you can't do that) and then ran:
sp_dropserver <old_name\instancename> GO sp_addserver <new_name\instancename>, local GOBut when I did aselect @@servernameI kept getting the old server name...So when I rebooted the machine (standard practise when things seem weird..) the instance came back upand when I selected the @@ servername I got the new name...HTHPJFINTRAX at 2007-9-9 >
Hi All,
I thought I would reuse this append.....
I would like to rename a windows 2003 server with sql server 2005 on top of it....
I have tried all the tricks in these appends and the server renames just fine. However report services can no longer connect......I have even changed the userid in the users table in report server.
I get the following message when trying to connect to report services.
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I then even tried to remove sql server from the machine so I could re-install it and it refuses to delete from the machine.....even when I go through setup and say 'remove'....afther the 'remove' it is still there.
Could someone please be so kind as to advise me either.
1. How do I remove sql server 2005 from an windows 2003 server? or
2. How might I go forward and get report services working again?
This is all on win 2003 server, sql server 2005 sp2. And all inside a vmware machine.
All advice most appreciated.
Best Regards
Peter
^^^ Ditto. Brand new Server 2003 R2 box, sysprep'd from a ghost image, ranamed the machine, joined the domain, SQL went belly-up. After executing sp_dropserver and sp_addserver, I got my 2 instances (SQLSERVER and SQLSERVEREXPRESS) working, but I still can't install the SQL Server 2005 service pack because it keeps coming up with the original instance name (OLDMACHINE\ReportServer) and, of course, it can't authenticate to it.
Can anyone figure out how to rename the default ReportServer instance?
Regards,
Lloyd
Hi Lloyd,
for me it looks like there are some permissions that still have the old machine name and I have been unable to figure out how to change those permissions.....for me it would be enough just to figure out how to get rid of sql server off the VM and re-install it......if nothing else works I will have to build a brand new vm from scratch.......sigh......
I'll let you know if I find out a way to do this...glad to know others have the same problem...I don't feel quite so ignorant.....though I have asked my SQL 'certified' guys here and they can't see what the problem is either...
Thanks
Peter
Ahah, I may at least be of some help there then... Last week, I ran across a KB article that detailed a manual removal of SQL Server (200 or 2005, I don't recall which, sorry), regarding both artifact files AND registry settings.
In my case, I would like to remove just ReportServices and reinstall it. 
