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.

Basic Edition instances do not have secondary instances for hot backup. Therefore, an instance may remain unavailable for an extended period of time if it fails, changes specifications, or undergoes a version upgrade.

High-availability Edition instances each have a secondary instance. Data between the primary and secondary instances is synchronized in real time. If the primary instance cannot be accessed, your business is automatically switched to the secondary instance. In addition, High-availability Edition instances provide complete product features, including auto scaling, backup and recovery, performance optimization, and read/write splitting.

For information about the functional differences between different versions and editions, see Functions supported by different versions and editions of SQL Server.

Billing description

For information about the billing for version upgrade, see Billing details about configuration change.

Impact

After the upgrade is complete, you must switch over services. The downtime caused by the switchover varies depending on the instance size. In most cases, the switchover can be completed within 20 minutes. We recommend that you switch over services during system maintenance. Make sure each application can be reconnected in the event of disconnection.

Prerequisites

An SQL Server Basic Edition instance is available.
Note You can view the edition of the instance on the Basic Information page.Basic Information page

Precautions

  • Your instance cannot be rolled back to earlier versions or editions after the upgrade is complete.
    Warning We recommend that you create a pay-as-you-go instance to test the version or edition compatibility before the upgrade.
  • The following table lists the upgrade rules.
    Table 1. Upgrade rules
    Original version or edition Higher available version or edition
    2016 Enterprise Edition (Basic Edition) 2016 Enterprise Edition (High-availability Edition)
    2012 Enterprise Edition (Basic Edition) 2016 Enterprise Edition (High-availability Edition)
    2012 Enterprise Edition (High-availability Edition)
    2016 Standard Edition (Basic Edition) 2016 Standard Edition (High-availability Edition)
    2016 Enterprise Edition (High-availability Edition)
    2012 Standard Edition (Basic Edition) 2016 Enterprise Edition (High-availability Edition)
    2016 Standard Edition (High-availability Edition)
    2012 Enterprise Edition (High-availability Edition)
    2012 Standard Edition (High-availability Edition)
    2016 Web Basic Edition 2016 Enterprise Edition (High-availability Edition)
    2016 Standard Edition (High-availability Edition)
    2012 Web Basic Edition 2016 Enterprise Edition (High-availability Edition)
    2016 Standard Edition (High-availability Edition)
    2012 Enterprise Edition (High-availability Edition)
    2012 Standard Edition (High-availability Edition)

Procedure

  1. Log on to the ApsaraDB for RDS console.
  2. Select the target region.Select a region
  3. Find the target RDS instance and click the instance ID.
  4. On the Basic Information page, click Upgrade Version. In the message that appears, click Confirm.
  5. On the Upgrade Engine Version page, modify your instance configurations as follows.
    Parameter Description
    Upgrade To Select the target version. The Edition, Storage Type, and Instance Type settings vary depending on the selected target version.
    Edition Select High-availability: The classic high-availability architecture allows your instance to work in primary/secondary mode to achieve balanced performance in all aspects.
    Storage Type
    • Standard SSD: an elastic block storage device based on the distributed storage architecture. You can separate computing and storage from each other by storing data in a standard SSD.
    • Enhanced SSD: an ultra-high performance cloud disk provided by Alibaba Cloud. Enhanced SSDs are based on the next-generation distributed block storage architecture, a 25 GE network, and remote direct memory access (RDMA) technology. They can deliver up to 1 million random IOPS per disk and have low latency.
    Zone Select the zone to which you want to migrate your instance. Multi-zone migration is supported.
    CPU and Memory Each instance type supports a specific number of CPU cores, memory, maximum number of connections, and maximum IOPS. For more information, see Instance types.
    Network Type Classic Network is unavailable. You must specify the VPC information.
    • If your instance is accessed through a classic network before the upgrade, you can change its network type to VPC and configure a VSwitch.
    • If your instance is accessed through a VPC or through both a classic network and a VPC before the upgrade, you are not allowed to change its VPC. However, you can change its VSwitch.
    VSwitch Select the target VSwitch. If you select multiple zones for your instance, you must select multiple target VSwitches.
    Note
    • If your instance is accessed through a VPC or through both a classic network and a VPC before the upgrade, you are not allowed to change its VPC. However, you can change its VSwitch. The available VSwitches vary depending on the specified zone and VPC.
    • If you select the default VPC, the target VSwitch can be either the default VSwitch or a non-default VSwitch.
    • Otherwise, the target VSwitch can only be a non-default VSwitch.
    Switching Time
    • Switch Immediately After Data Migration: Data is migrated and services are switched over immediately.
    • Switch Within Maintenance Window: Data is migrated, and services are switched over later during a maintenance period.
    Upgrade configuration
  6. Select the terms of service and click Confirm.

Change the database connection address

After the upgrade, the instance can only be accessed through a VPC. The following table describes how to change the database connection address for the instance after the upgrade based on the original network type of the instance.

Original network type Change rule
Classic network The instance after the upgrade is accessed through both a classic network and a VPC:
  • The original connection address of the classic network still applies to the instance after the upgrade. This address does not expire.
  • A VPC connection address is generated for the instance after the upgrade based on the VPC that is specified during the upgrade.
VPC The instance after the upgrade is accessed still through a VPC. The original VPC connection address still applies to the instance after the upgrade, but the virtual IP address (VIP) may change.
Classic network and VPC The instance after the upgrade is accessed still through both a classic network and a VPC. The original classic network and VPC connection addresses still apply to the instance after the upgrade. The expiration time of the classic network connection address remains unchanged.