Switch an ApsaraDB RDS for SQL Server instance to a different vSwitch within the same zone — without rebuilding the instance. The switch causes a network interruption of approximately 30 seconds and changes the virtual IP address (VIP) of the instance.
To switch the vSwitch for an instance running a different database engine, see Switch the VPC or vSwitch for an ApsaraDB RDS for MySQL instance or Switch the vSwitch for an ApsaraDB RDS for PostgreSQL instance.
Prerequisites
Before you begin, ensure that you have:
An instance with enterprise SSD (ESSD) or standard SSD as the storage type (serverless instances are also supported)
Impacts
| Impact | Details |
|---|---|
| Network interruption | The switch causes a network interruption lasting approximately 30 seconds. Configure your application to reconnect automatically. |
| VIP change | Switching the vSwitch changes the virtual IP address (VIP). Connect to the instance using its endpoint rather than the IP address to avoid connection issues caused by VIP changes. |
| Service reconnection | The VIP change temporarily disrupts connections from Data Management (DMS) and Data Transmission Service (DTS). Both services reconnect automatically once the switch completes. |
| Client-side cache | Cached data on the client side may become read-only after the switch. Clear the cache to restore write operations. |
Switch the vSwitch
Go to the Instances page. In the top navigation bar, select the region where the instance resides. Find the instance and click its ID.
In the left navigation pane, click Database Connection, then click Switch vSwitch.
Select a target vSwitch and click OK.
NoteThe target vSwitch must be in the same zone as the instance. To create a VPC or vSwitch, go to the VPC console.
Only ApsaraDB RDS for SQL Server 2008 R2 instances using cloud disks support VPC changes. Other versions do not support direct VPC switching. If your instance does not support direct VPC changes, purchase a new ApsaraDB RDS instance with the destination VPC selected during purchase, then migrate the data to the new instance.
In the dialog box, review the risks of the switch and click OK.
What's next
To switch the instance to a vSwitch in a different zone, see Migrate an instance across zones.
To perform the switch programmatically, call the SwitchDBInstanceVpc API operation.