This topic describes how to upgrade an ApsaraDB RDS for SQL Server instance from Basic Edition to High-availability Edition. During the upgrade, you can also upgrade the SQL Server version.

Background information

In the Basic Edition, your RDS instance does not have a secondary RDS 'instance as a hot standby. For more information, see RDS Basic Edition. If you are changing the specifications or upgrading the SQL Server version of your RDS instance, your database service becomes unavailable. If your RDS instance fails unexpectedly, your database service also becomes unavailable. The unavailability may last for a long period of time.

In the High-availability Edition, your RDS instance has a secondary RDS instance as a hot standby. For more information, see High-availability Edition. Data is synchronized in real time between your RDS instance and its secondary RDS instance. If your RDS instance cannot be connected, your workloads are automatically switched over to the secondary RDS instance. The High-availability Edition provides a complete suite of features, including auto scaling, backup and restoration, performance optimization, and read/write splitting.

Note For more information about the features that are provided by different SQL Server versions on each RDS edition, see Features of ApsaraDB RDS instances that run different SQL Server versions and RDS editions.

Prerequisites

Your RDS instance runs RDS Basic Edition.
Note You can log on to the ApsaraDB RDS console, find the RDS instance, and then go to the Basic Information page to view the edition of the RDS instance.

Precautions

  • After the upgrade is complete, your RDS instance cannot be rolled back to an earlier version or edition.
    Warning Before you start the upgrade, we recommend that you create a pay-as-you-go RDS instance that uses the destination SQL Server version and RDS edition. Also, configure other settings for this new RDS instance the same as those of your existing RDS instance. Then, you can test the compatibility between the two instances. For more information, see Create an ApsaraDB RDS for SQL Server instance.
  • The following table lists upgrade rules.
    Source SQL Server version and RDS edition Destination SQL Server version and RDS edition
    SQL Server 2016 EE on RDS Basic Edition SQL Server 2016 EE on RDS High-availability Edition
    SQL Server 2012 EE Basic on RDS Basic Edition SQL Server 2016 EE on RDS High-availability Edition
    SQL Server 2012 EE on RDS High-availability Edition
    SQL Server 2016 SE on RDS Basic Edition SQL Server 2016 SE on RDS High-availability Edition
    SQL Server 2016 EE on RDS High-availability Edition
    SQL Server 2012 SE on RDS Basic Edition SQL Server 2016 EE on RDS High-availability Edition
    SQL Server 2016 SE on RDS High-availability Edition
    SQL Server 2012 EE on RDS High-availability Edition
    SQL Server 2012 SE on RDS High-availability Edition
    SQL Server 2016 Web on RDS Basic Edition SQL Server 2016 EE on RDS High-availability Edition
    SQL Server 2016 SE on RDS High-availability Edition
    SQL Server 2012 Web on RDS Basic Edition SQL Server 2016 EE on RDS High-availability Edition
    SQL Server 2016 SE on RDS High-availability Edition
    SQL Server 2012 EE on RDS High-availability Edition
    SQL Server 2012 SE on RDS High-availability Edition
  • After the upgrade is complete, you must switch over your workloads. The downtime caused by the switchover varies based on the data volume of your RDS instance. In most cases, the switchover requires approximately 20 minutes. We recommend that you switch over your workloads during the specified maintenance window. Make sure that your applications are configured to automatically reconnect to your database system.

Fee

For more information about the upgrade fees, see Specification change fees.

Procedure

  1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
  2. In the Configuration Information section of the Basic Information page, click Upgrade Version. In the message that appears, click OK.
  3. On the Upgrade Engine Version page, configure the following parameters.
    Parameter Description
    Upgrade To Select the destination SQL Server version. The available Edition and Instance Type vary based on the selected destination SQL Server version. For more information, see the upgrade rules described in this topic.
    Edition
    • Select High-availability. The High-availability Edition allows your RDS instance to stand as a primary instance and have a secondary instance as a hot standby. The primary and secondary RDS instances work in the classic high-availability architecture to achieve balanced performance in all aspects.
    Note For more information about the RDS editions, see Overview.
    Instance Type Select the new specifications. Each instance type supports a specific number of cores, memory capacity, maximum number of connections, and maximum IOPS. For information, see Primary ApsaraDB RDS instance types.
    Switching Time
    • Select the time when you want to switch your workloads over to High-availability Edition. Switch Immediately After Data Migration: Data is migrated and workloads are switched over immediately.
    • Switch Within Maintenance Window: Data is migrated immediately, and workloads are switched over during the specified maintenance window.
  4. Read and select Terms of Service and click Pay Now.
  5. In the message that appears, click OK.