— by Ginger Keys
Recently a client of mine moved their production SQL Server Cluster to a new physical environment. When the time came to ‘go-live’ with the new environment, the client wanted the new SQL cluster name and IP address (SQLCLUSTERTEMP) to be renamed to the original, legacy name and IP address (SQLCLUSTER).
Renaming a SQL cluster name and IP address is easily done through Failover Cluster Manager:
In order to verify the rename we run this statement in SQL Server Management Studio (SSMS):
However after running this statement to verify the rename, SQL returned the old Cluster name (SQLCLUSTERTEMP). What happened!?
After renaming a SQL server name, you must execute the following statement in SSMS:
EXEC sp_dropserver ‘OLDSERVERNAME’ — (SQLCLUSTERTEMP)
EXEC sp_addserver ‘NEWSERVERNAME’, local — (SQLCLUSTER)
Once done, restart the SQL Services.
To check both the local server name and the virtual SQL cluster name, run both of these statements:
SELECT @@SERVERNAME –Local server name
SELECT SERVERPROPERTY(‘MACHINENAME’) –Windows computer name, or Virtual name if clustered
These statements normally return the same results, but in our case, they returned different values and the @@SERVERNAME was still incorrect. In fact, the results returned a NULL value for the @@SERVERNAME, and an error stating the Servername (SQLCLUSTER) already exists.
If this happens with your environment, run the following statement dropping and adding the same server name:
EXEC sp_dropserver ‘NEWSERVERNAME’ — (SQLCLUSTER)
EXEC SP_addserver ‘NEWSERVERNAME’,‘LOCAL’ — (SQLCLUSTER)
Restart the SQL Server Service again, and this should clear up any confusion SQL was having, and will return the correct name.
For more information about blog posts, concepts and definitions, further explanations, or questions you may have…please contact us at SQLRx@sqlrx.com. We will be happy to help! Leave a comment and feel free to track back to us. Visit us at www.sqlrx.com!
Please log in again. The login page will open in a new tab. After logging in you can close it and return to this page.
I have always found this particular “feature” annoying. It seems that MS could provide a clean, straightforward method for renaming a server, an instance, and/or a cluster.