You can create a temporary instance, restore data to the temporary instance, log on to the temporary instance to check whether the data is correct, and then restore the data from the temporary instance to the destination instance. This topic describes how to log on to a temporary instance.
PrerequisitesYour RDS instance runs one of the following SQL Server versions and RDS editions:
- SQL Server 2012 Basic Edition
- SQL Server 2016 Basic Edition
- SQL Server 2008 R2 (with local SSDs)
Log on to a temporary instance
You can log on to temporary instances through the internal network. The internal network is fast, secure, and free of traffic charges.
Log on to a temporary instance by using an ECS-based client
- Create an ECS instance to access the temporary ApsaraDB for RDS instance. The ECS
instance must meet the following requirements:
- The ECS instance is located in the same region as the RDS instance.
- The network type is classic network. This is because ECS and RDS instances must have the same network type to communicate through the internal network and the network type of all temporary RDS instances is classic network.
- Add the internal IP address of the ECS instance to the whitelist of the temporary RDS instance.
- Log on to the ECS instance. For more information, see Overview.
- Access the temporary RDS instance from the ECS instance. For more information, see the "Use a client to connect to an instance" section in Connect to an ApsaraDB RDS for SQL Server instance.