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

In the Basic Edition, your RDS instance does not have a secondary instance as a hot standby. For more information, see 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.

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 instance. If your RDS instance cannot be connected, your workloads are automatically switched over to the secondary instance. The High-availability Edition provides a complete suite of features, including auto scaling, backup and restoration, performance optimization, and read/write splitting.

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.

Fee

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

Impacts

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.

Prerequisites

Your RDS instance runs Basic Edition.
Note You can view the edition of your RDS instance on the Basic Information page.

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.
    Table 1. 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

Procedure

  1. Go to the ApsaraDB RDS console.
  2. Select the target region.
  3. Find the primary RDS instance and click its ID.
  4. On the Basic Information page, click Upgrade Version. In the message that appears, click OK.
  5. On the Upgrade Engine Version page, configure the following parameters.
    Parameter Description
    Upgrade To Select the destination SQL Server version. The available Edition, Storage Type, and CPU and Memory settings vary based on the selected destination SQL Server version.
    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.
    Storage Type
    • Standard SSD: A standard SSD is an elastic block storage device that is designed based on the distributed storage architecture. You can store data on standard SSDs to separate computing from storage.
    • Enhanced SSD: An enhanced SSD is an ultra-high performance disk that is designed by Alibaba Cloud based on the next-generation distributed block storage architecture. It integrates 25 Gigabit Ethernet and remote direct memory access (RDMA) technologies. This reduces one-way latency and delivers up to 1 million random input/output operations per second (IOPS).
    Zone Select the destination zone. Multi-zone deployment is supported.
    CPU and Memory Select the new specifications. Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary instance types.
    Network Type Classic Network is unavailable. You must specify the VPC information.
    • If your RDS instance is connected over the classic network before the upgrade, you can change its network type to VPC and configure a vSwitch.
    • If your RDS instance is connected over a VPC or over both the classic network and a VPC before the upgrade, you cannot change its VPC. However, you can change its vSwitch.
    vSwitch Select the destination vSwitch. If you select multiple zones for your RDS instance, you must select multiple destination vSwitches.
    Note
    • If your RDS instance is connected over a VPC or over both the classic network and a VPC before the upgrade, you cannot change its VPC. However, you can change its vSwitch. The available vSwitches vary based on the specified zone and VPC.
    • If you select the default VPC, the destination vSwitch can be either the default vSwitch or a custom vSwitch.
    • If you do not select the default VPC, the destination vSwitch must be a custom vSwitch.
    Switching Time
    • 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.
    Upgrade configuration
  6. Select Product Terms of Service and click Confirm.

Change the endpoints of your RDS instance

After the upgrade, your RDS instance resides in a VPC. The following table describes how to change the endpoints of your RDS instance after the upgrade based on the original network type of your RDS instance.

Original network type Change rule
Classic network After the upgrade, your RDS instance is connected over both the classic network and a VPC:
  • The original classic network endpoint remains available and never expires.
  • A VPC endpoint is generated for your RDS instance based on the specified VPC.
VPC After the upgrade, your RDS instance is connected over a VPC. The original VPC endpoint remains available. However, the virtual IP address (VIP) that is bound to the original VPC endpoint may change.
Classic network and VPC After the upgrade, your RDS instance is connected over both the classic network and a VPC. The original classic network and VPC endpoints remain available. The expiration time of the classic network endpoint remains unchanged.