--- title: "Rename computer hosting instance" description: When you rename a computer that hosts an instance of SQL Server, update the system metadata stored in sys.servers. ms.custom: "seo-lt-2019" ms.date: "12/13/2019" ms.prod: sql ms.reviewer: "" ms.technology: install ms.topic: conceptual helpviewer_keywords: - "remote login errors [SQL Server]" - "standalone computer names [SQL Server]" - "names [SQL Server], standalone instances of SQL Server" - "renaming standalone instances of SQL Server" - "sysservers system table" - "removing remote logins" - "deleting remote logins" - "dropping remote logins" ms.assetid: bbaf1445-b8a2-4ebf-babe-17d8cf20b037 author: MashaMSFT ms.author: mathoma monikerRange: ">=sql-server-2016||=sqlallproducts-allversions" --- # Rename a Computer that Hosts a Stand-Alone Instance of SQL Server [!INCLUDE [SQL Server -Windows Only](../../includes/applies-to-version/sql-windows-only.md)] When you change the name of the computer that is running [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], the new name is recognized during [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] startup. You do not have to run Setup again to reset the computer name. Instead, use the following steps to update system metadata that is stored in sys.servers and reported by the system function @@SERVERNAME. Update system metadata to reflect computer name changes for remote connections and applications that use @@SERVERNAME, or that query the server name from sys.servers. The following steps cannot be used to rename an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. They can be used only to rename the part of the instance name that corresponds to the computer name. For example, you can change a computer named MB1 that hosts an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] named Instance1 to another name, such as MB2. However, the instance part of the name, Instance1, will remain unchanged. In this example, the \\\\*ComputerName*\\*InstanceName* would be changed from \\\MB1\Instance1 to \\\MB2\Instance1. **Before you begin** Before you begin the renaming process, review the following information: - When an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is part of a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] failover cluster, the computer renaming process differs from a computer that hosts a stand-alone instance. - [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] does not support renaming computers that are involved in replication, except when you use log shipping with replication. The secondary computer in log shipping can be renamed if the primary computer is permanently lost. For more information, see [Log Shipping and Replication (SQL Server)](../../database-engine/log-shipping/log-shipping-and-replication-sql-server.md). - When you rename a computer that is configured to use [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)], [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] might not be available after the computer name change. For more information, see [Rename a Report Server Computer](../../reporting-services/report-server/rename-a-report-server-computer.md). - When you rename a computer that is configured to use database mirroring, you must turn off database mirroring before the renaming operation. Then, re-establish database mirroring with the new computer name. Metadata for database mirroring will not be updated automatically to reflect the new computer name. Use the following steps to update system metadata. - Users who connect to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] through a Windows group that uses a hard-coded reference to the computer name might not be able to connect to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. This can occur after the rename if the Windows group specifies the old computer name. To ensure that such Windows groups have [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] connectivity following the renaming operation, update the Windows group to specify the new computer name. You can connect to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using the new computer name after you have restarted [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. To ensure that @@SERVERNAME returns the updated name of the local server instance, you should manually run the following procedure that applies to your scenario. The procedure you use depends on whether you are updating a computer that hosts a default or named instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. ## Rename a computer that hosts a stand-alone instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] - For a renamed computer that hosts a default instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], run the following procedures: ```sql sp_dropserver ; GO sp_addserver , local; GO ``` Restart the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. - For a renamed computer that hosts a named instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], run the following procedures: ```sql sp_dropserver ; GO sp_addserver , local; GO ``` Restart the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. ## After the Renaming Operation After a computer has been renamed, any connections that used the old computer name must connect by using the new name. ## Verify renaming operation - Select information from either @@SERVERNAME or sys.servers. The @@SERVERNAME function will return the new name, and the sys.servers table will show the new name. The following example shows the use of @@SERVERNAME. ``` SELECT @@SERVERNAME AS 'Server Name'; ``` ## Additional considerations **Remote Logins** - If the computer has any remote logins, running **sp_dropserver** might generate an error similar to the following: `Server: Msg 15190, Level 16, State 1, Procedure sp_dropserver, Line 44 There are still remote logins for the server 'SERVER1'.` To resolve the error, you must drop remote logins for this server. ### Drop remote logins - For a default instance, run the following procedure: ```sql sp_dropremotelogin old_name; GO ``` - For a named instance, run the following procedure: ```sql sp_dropremotelogin old_name\instancename; GO ``` **Linked Server Configurations** - Linked server configurations will be affected by the computer renaming operation. Use **sp_addlinkedserver** or **sp_setnetname** to update computer name references. For more information, see the [sp_addlinkedserver (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-addlinkedserver-transact-sql.md) or [sp_setnetname (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-setnetname-transact-sql.md). **Client Alias Names** - Client aliases that use named pipes will be affected by the computer renaming operation. For example, if an alias "PROD_SRVR" was created to point to SRVR1 and uses the named pipes protocol, the pipe name will look like `\\SRVR1\pipe\sql\query`. After the computer is renamed, the path of the named pipe will no longer be valid and. For more information about named pipes, see the [Creating a Valid Connection String Using Named Pipes](https://go.microsoft.com/fwlink/?LinkId=111063). ## See also [Install SQL Server](../../database-engine/install-windows/install-sql-server.md)