SQL Clone
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

Changing Your SQL Server Name

Reading Time: 2 minutes
Is the name of your SQL Server correct?

Is the name of your SQL Server correct?

Why Worry About The Server Name In SQL?

When the name of the actual host machine’s server name does not match the server name stored in SQL Server a lot of things can start to go wrong.

Reporting services can break, Connections denied, maintenance plans fail. Generally chaos can happen, but not always right away.

How does these names get out of sync? Usually is is from some sort of move or rebuild of a server. I experienced it with one client that physically moved data centers, and in the process decided they wanted to change the IP address and name for every server. We are talking thousands of servers moved, and every one of them renamed. That included over 750 SQL Servers.

I came onto the project after the move had been done and it took a while to realize that a lot of maintenance plans were failing. Turns out that the detailed checklist for the data center move, including renaming the servers, had left out the critical step of resetting the server name on each SQL Server. Production and development system were affected and needless to say it made for a fun week to get everything fixed as fast as possible.


There are a few exceptions to remain aware of when you are looking to rename a SQL Server:

  • Fail-over Clusters – When as instance is part of a SQL Server fail-over cluster, the renaming process outlined here will not work.
  • Replication – renaming computers involved in replication, except for log shipping with replication, as not supported. You need to remove replication for the change to be able to be done. Be sure to script out all your settings first so you can more easily rebuild it after the server name change. If you are using log shipping with replication and you completely lose the primary, you can rename the secondary. You can get more info on this scenario in the MSDN library here: Log Shipping and Replication (SQL Server)
  • Reporting Services – After a rename, reporting services may not be available. To fix this you need to edit the RSReportServer.config file in a couple of ways. Details can be found in MSDN here: Rename a Report Server Computer.
  • Database Mirroring – Mirroring needs to be turned off prior to changing the server name. Then once renamed you will need to re-establish the mirror using the new server name. Metadata for mirroring foes not update automatically.
  • Windows groups – If using a hard-coded reference to the server name. This occurs if the Windows group specifies the old computer name. You would need to update the Windows group after the name change to specify the new server name.

Now that that is all out of the way, let’s get to actually changing our server name.

Changing the Server Name

First you are going to want to check if there are any remote logins. If you have any remote logins, that reference the old server name, you will receive an error when you try to change the server name.

This script will check your server for any remote logins so you can remove them.

    sl.remote_name as RemoteLoginName, 
from sys.remote_logins sl 
inner join sys.sysservers ss on 
    sl.server_id = ss.srvid

Be sure to record the remote logins so you can recreate them afterwards.

To drop any remote logins you may be found, you can use the following syntax:

-- For a default instance
sp_dropremotelogin <old_physical_server_name>
-- For a named instance
sp_dropremotelogin '<old_physical_server_name\instancename>'

Once the remote logins are out, you can go ahead and change the name of the server with this script:

-- verify name incorrect
SELECT @@servername;

-- Remove the old name from the SQL server
sp_dropserver '<name from @@servername>';

-- Add the new name, with local set as well.
sp_addserver '<new server name>',LOCAL;

-- verify change taken
SELECT @@servername;

To add the remote logins back after you have changed the server name you can use the following syntax:

    @remoteserver = '<remoteserver>', 
    @loginame = ] '<login>', 
    @remotename = '<remote_name>'

After all the changes have been made you will need to restart the SQL Server service to be able to connect with the new server name.


Who is Chris?

Chris Bell, SQL Server MVP, MCSE & MCITP, is a 20 year veteran of using Microsoft products & SQL Server to create solutions for businesses, organizations and individuals. Chris speaks, blogs, writes articles and makes media of all kinds regarding SQL Server at WaterOxConsulting.com.

Click here to contact Chris or to follow him on twitter.

Chris is also the founder of WaterOx Consulting, Inc. which features SQL Server consulting services along with the destination location week-long training series: SQL Summer Camp. New in 2015 WaterOx Consulting is introducing the SQLPunch series of half day training events designed to help others learn to efficiently and effectively use SQL Server.

He is the founding president of PASSDC and organizes the annual SQLSaturday for the DC area. Chris frequently speaks at and attends SQL Server events, sharing his passion for all things SQL Server.

In 2012 Chris was a finalist in the worldwide Exceptional DBA competition and in 2014 he received the Microsoft MVP award in recognition of his open sharing of his knowledge with the technical community. His blog is currently syndicated to SQLServerCentral.com and ToadWorld.com


The post Changing Your SQL Server Name appeared first on WaterOx Consulting.

WaterOx SQL

Chris Bell (MCITP) has been working with Microsoft technologies for over 20 years and using SQL Server for over 18 of those years. He is currently the Owner and Lead consultant for WaterOx Consulting, a Maryland based company focused on helping clients, that can’t afford or justify a full time data team, get the most from their SQL Server environments. For more information please visit WateroxConsulting.com.


Leave a comment on the original post [wateroxconsulting.com, opens in a new window]

Loading comments...