How to Rename SQL Server Network Name (Virtual Server Name) in SQL Server 2019 Failover Cluster Instance (FCI).


In SQL Server Failover Cluster Instance (FCI), the SQL Server Network Name (also called the Virtual Server Name) is what applications and users use to connect. Sometimes, we may need to rename to match new naming standards or after a migration.

This blog explains the recommended way to rename the SQL Server Network Name in SQL Server 2019 FCI, along with key points to check after the change.

Environment details:

Component

Name

Version

Purpose

Node 1

sql01-chn.corp.local

Windows Server 2019

First cluster server

Node 2

sql02-chn.corp.local

Windows Server 2019

Second cluster server

Cluster Name

WINSQLPRD01

 

Windows failover cluster name

SQL Network Name

Before: CHNSQLVS01-MIG
After: CHNSQLVS01

SQL Server 2019

Name used by applications to connect

SQL Instance ID

PRD01

SQL Server 2019

SQL Server instance name

 

1. Open Failover Cluster Manager by pressing Win + R, typing cluadmin.msc and clicking OK.


2. In Failover Cluster Manager, navigate to Roles → SQL Server (PRD01) → Resources tab, select the Server Name (CHNSQLVS01-MIG) resource and right-click to open Properties.




3. Rename the SQL Server network name from CHNSQLVS01-MIG to CHNSQLVS01, SQL Server resource and its dependent resources will go offline and then come back online.









4. From Failover Cluster Manager, confirm the SQL Server network name reflects the new VNN.



5. Review cluster events for any errors and ensure the new Virtual Server Name (VNN) is updated in Active Directory (AD) and DNS.







6. Old Virtual Server Name CHNSQLVS01-MIG is no longer resolvable in DNS, while the new Virtual Server Name CHNSQLVS01 resolves successfully and the SQL query SELECT @@SERVERNAME confirms the instance name as CHNSQLVS01\PRD01.



7. Flush and re-register DNS on the client machines if needed.

ipconfig /flushdns

ipconfig /registerdns

nbtstat –RR



Comments

Post a Comment

Popular posts from this blog

Step-by-Step Guide to Configure Oracle GoldenGate Plug-in for Enterprise Manager 13cR5

Image
Oracle GoldenGate Enterprise Manager Plug-in helps monitor and manage Goldengate processes through Oracle Enterprise Manager Cloud Control. Environment details: Host: srvdb01.localdomain Operating System: OEL 8.8 OEM Version: 13.5.0.0 OEM Home: /u01/app/oracle/em13c/oraclehome Database Version: 19.23.0.0.0 Database Home: /u01/app/oracle/product/19.0.0/dbhome_1 Goldengate Version: 21.3.0.0.0 Goldengate Home: /u01/app/oracle/product/21.3.0/ogg_1 Goldengate Agent Home: /u01/app/oracle/oggmon_agent122   All components, including Oracle Enterprise Manager 13.5, Oracle Database 19c, Oracle Goldengate 21.3 and Goldengate Monitor Agent 12.2 are configured on the same host srvdb01.localdomain running on OEL 8.8. We will set up the Oracle GoldenGate Plug-in for Enterprise Manager 13cR5. 1. Download the Oracle Goldengate Plug-in for OEM 13.5 from edelivery.oracle.com. https://www.oracle.com/middleware/technologies/goldengate-downloads.html 2. Copy the Oracle Goldengate Plug-in to the OMS ...
Read more

How to Reposition Extract, Data Pump and Replicat in GoldenGate During Trail File Corruption

In this blog, we will walk you through the steps to reposition the Extract, Data Pump and Replicat processes in the event of Extract trail file corruption.   The environment consists of: Host: dbsrv01.localdomain: Source Database (19c) named "master" running on OEL 8.8, Extracting HR.REGIONS table using GoldenGate 21.3. Host: dbsrv02.localdomain: Target Database (19c) named "orcl" running on OEL 8.8, Replicating HR.REGIONS table using GoldenGate 21.3. Source (master) Target (orcl) 1. We have an integrated Extract running on the source database.   [oracle@dbsrv01 ~]$ ggsci   Oracle GoldenGate Command Interpreter for Oracle Version 21.3.0.0.0 OGGCORE_21.3.0.0.0_PLATFORMS_210728.1047_FBO Oracle Linux 7, x64, 64bit (optimized), Oracle Database 21c and lower supported versions on Jul 29 2021 03:59:23 Operating system character set identified as UTF-8.   Copyright (C) 1995, 2021, Oracle and/or its...
Read more

Step-by-Step Guide to Configure Oracle GoldenGate Veridata 23c

Image
Oracle Goldengate Veridata is a fast tool that compares data between source and target databases, report differences and fixes them. Oracle GoldenGate Veridata 23c supports only MySQL Server as the repository database for storing metadata. The environment consists of: Host: dbsrv01.localdomain : Veridata Agent 23c, Source Database (19c) running on OEL 8.8, extracting  HR.REGIONS table using GoldenGate 21.3 Host: dbsrv02.localdomain : Veridata Agent 23c, Target Database (19c) running on OEL 8.8, replicating HR.REGIONS table using GoldenGate 21.3 Host: dbsrv03.localdomain : Veridata Server 23c, running on OEL 8.8 We will set up the Veridata Server and Veridata Agent 23c for data comparison and synchronization. 1. Download the Oracle Goldengate Veridata installation file from Oracle Software Delivery Cloud. 2.   Copy the Oracle Goldengate Veridata installer to the target server and unzip under /tmp. [oracle@dbsrv03 ~]$ cd /tmp [or...
Read more