If your business needs change, you can switch the vSwitch for your ApsaraDB RDS for SQL Server instance in the RDS console or by calling an API operation.
To switch the vSwitch for an instance that runs a different database engine, see the following topics:
Prerequisites
Your instance must use either ESSD or standard SSD storage. Serverless instances are also supported.
Impacts
-
The switching process causes a brief network interruption of about 30 seconds. Ensure your application has an automatic reconnection mechanism.
-
Switching a vSwitch changes the Virtual IP (VIP). You should use the endpoint instead of an IP address to connect in your application.
-
A VIP change will temporarily affect DMS and DTS. Normal operations will resume automatically after the change is complete.
-
Client-side caching may prevent write operations and allow only read operations. If this issue occurs, clear the client-side cache.
Procedure
Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
-
In the navigation pane on the left, click Database Connection. Then, click Switch vSwitch.
-
Select a vSwitch and click OK.
Note-
You can switch only to a vSwitch in the same zone as the instance. To create a VPC or vSwitch, go to the VPC console.
-
Currently, only ApsaraDB RDS for SQL Server 2008 R2 instances that use cloud disks support VPC switching. Other instance versions do not support this operation. If your instance does not support a direct VPC switch, you can purchase a new RDS instance (select the destination VPC during the purchase) and then migrate the data to the new instance.
-
-
In the dialog box that appears, review the risks and click OK.
Related topics
-
To switch the instance to a vSwitch in a different zone, see Migrate an instance across zones.
-
You can also switch the vSwitch by using the API. For more information, see Switch the VPC and vSwitch of an RDS instance.