This topic describes how to manually restart an ApsaraDB RDS for SQL Server instance. This applies if the number of connections exceeds the specified threshold or a performance issue occurs.

Impacts

A restart causes a network interruption that lasts about 30 seconds. Before you restart your RDS instance, we recommend that you make proper service arrangements. Proceed with caution.
Note The Basic Edition does not provide a secondary RDS instance as a hot standby for the primary RDS instance. If the primary RDS instance unexpectedly exits, your database service may be unavailable for a long period of time. If you change the specifications or upgrade the database engine version of the primary RDS instance, your database service may also be unavailable for a long period of time. If you require high service availability, we recommend that you do not select the Basic Edition. For example, you can select the High-availability Edition. Some primary RDS instances support the upgrade from the Basic Edition to the High-availability Edition. For more information, see Upgrade an RDS instance to the High-availability Edition.

Procedure

  1. Visit the RDS instance list, select a region above, and click the target instance ID.
  2. In the upper-right corner of the Basic Information page, click Restart Instance.
  3. In the message that appears, click OK.

Related operations

Operation Description
Restart an ApsaraDB for RDS instance Restarts an ApsaraDB RDS instance.