You can create a temporary ApsaraDB RDS for SQL Server instance for data restoration. You need to migrate the data of your source RDS instance to the temporary RDS instance, log on to the temporary RDS instance to check whether the data is correct, and then restore the data of the temporary RDS instance to the destination RDS instance. This topic describes how to log on to a temporary RDS instance.
Prerequisites
Your RDS instance meets the following requirements:
The RDS instance runs SQL Server 2008 R2.
The RDS instance runs RDS High-availability Edition.
The RDS instance uses local disks.
You can go to the Basic Information page of your RDS instance to view the preceding information.
Log on to a temporary RDS instance
You can log on to a temporary RDS instance over an internal network, which is fast, secure, and free of traffic charges. You can use the SQL Server Management Studio (SSMS) client of your Elastic Compute Service (ECS) instance to access the temporary RDS instance over an internal network.
Use the SSMS client of your ECS instance to log on to the temporary RDS instance
Create an ECS instance that is used to access the temporary RDS instance. The ECS instance must meet the following requirements:
The ECS instance resides in the same region as the temporary RDS instance.
The ECS instance uses the classic network type. This is because ECS and RDS instances must have the same network type to communicate over an internal network and all temporary RDS instances use the classic network type.
Add the private IP address of the ECS instance to an IP address whitelist of the temporary RDS instance.
Log on to the ECS instance. For more information, see Connection method overview.
Install and log on to the SSMS client on the ECS instance to access the temporary RDS instance. For more information, see Connect to an ApsaraDB RDS for SQL Server instance.
Related operations
Operation | Description |
CreateTempDBInstance | Creates a temporary instance. |