This topic describes how to log on to a temporary ApsaraDB RDS for SQL Server instance. After you create a temporary RDS instance for a primary RDS instance, ApsaraDB RDS restores data from the specified backup file to the temporary RDS instance. You can log on to the temporary RDS instance, verify that the restored data is correct, and then migrate the restored data from the temporary RDS instance to the primary RDS instance.
PrerequisitesThe temporary RDS instance runs one of the following SQL Server versions and RDS editions:
- SQL Server 2012 on RDS Basic Edition
- SQL Server 2016 on RDS Basic Edition
- SQL Server 2008 R2 (with local SSDs)
You can log on to a temporary RDS instance over an internal network, which is fast, secure, and free of traffic charges.
To log on to a temporary RDS instance by using an Elastic Compute Service (ECS)-based client, perform the following steps:
- 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 Overview.
- Access the temporary RDS instance from the ECS instance. For more information, see the "Use a database client to connect to your RDS instance" section in Connect to an ApsaraDB RDS for SQL Server instance.