This topic describes how to upgrade an ApsaraDB RDS for SQL Server instance with local SSDs from SQL Server 2008 R2 to SQL Server 2012 or 2016. During the upgrade, you can also migrate the RDS instance across zones.

Alibaba Cloud has stopped providing security updates for ApsaraDB RDS for SQL Server 2008 R2 instances that were purchased on and after July 9, 2019. For more information, see [Notice] Supplementary service agreement for ApsaraDB RDS for SQL Server 2008 R2. We recommend that you upgrade your SQL Server version at the earliest opportunity.

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 SQL Server 2008 R2 with local SSDs.
  • The total storage capacity of your RDS instance is no less than 20 GB.
  • The Transparent Data Encryption (TDE) feature is disabled for your RDS instance.
    Note If TDE is enabled, you must disable the TDE feature for all databases. Then, you must submit a ticket to disable TDE for your RDS instance.

Precautions

  • After the upgrade is complete, your RDS instance cannot be rolled back to an earlier version.
    Warning Before you start the upgrade, we recommend that you create a temporary RDS instance that runs the destination SQL Server version. 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 a temporary RDS instance that runs the destination SQL Server version.
  • You can upgrade your RDS instance with local SSDs from SQL Server 2008 R2 to the following versions:
    • SQL Server 2012 EE
    • SQL Server 2016 SE
    • SQL Server 2016 EE
  • If SSL is enabled for your RDS instance, you can upgrade the SQL Server version directly. After the upgrade is complete, the endpoints of your RDS instance remain unchanged, but SSL is disabled. You must enable SSL again. For more information, see Configure SSL encryption for an RDS instance.
  • If you upgrade your RDS instance to SQL Server 2012 EE or 2016 EE, the TDE feature remains available. If you upgrade your RDS instance to SQL Server 2016 SE, the TDE feature becomes unavailable.

Procedure

  1. Visit the RDS instance list, select a region above, and click the target instance ID.
  2. On the Basic Information page, click Upgrade Version. In the message that appears, click OK. Upgrade in the new ApsaraDB RDS console
  3. 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. The available vSwitches vary based on the specified zone and VPC.
    vSwitch Select the destination vSwitch. If you select multiple zones for your RDS instance, you must select multiple destination vSwitches.
    Note
    • 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
  4. 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 A VPC endpoint is generated for your RDS instance based on the specified VPC. This endpoint replaces the original VPC endpoint of your RDS instance.
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.

Create a temporary RDS instance that runs the destination SQL Server version

Before you start the upgrade, we recommend that you create a temporary RDS instance that runs the destination SQL Server version. 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.

Note You can create the temporary RDS instance only for an RDS instance that runs SQL Server 2008 R2 with TDE and SSL enabled.
  1. Visit the RDS instance list, select a region above, and click the target instance ID.
  2. In the left-side navigation pane, click Backup and Restoration.
  3. On the Temporary Instance tab, specify the point in time at which you want to clone data and click Create Temporary Instance of Higher Version. Create Temporary Instance of Higher Version button
  4. Configure the following parameters.
    Parameter Description
    Zone Select the zone in which you want to create the temporary RDS instance.
    Upgrade To Select the SQL Server version that the temporary RDS instance runs. Valid values:
    • 2016 SE
    • 2016 EE
    • 2012 EE
    VPC Select the VPC to which the temporary RDS instance belongs. You must select the VPC of the ECS instance to which you want to connect. Otherwise, the temporary RDS instance cannot communicate with the ECS instance over the internal network.
    vSwitch Select a vSwitch from the specified VPC.
    Note ApsaraDB RDS provides a default instance type and storage type for the temporary RDS instance. The temporary RDS instance is available for seven days. After the seven-day validity period elapses, ApsaraDB RDS releases the temporary RDS instance.
    Temporary RDS instance that runs the destination SQL Server version
  5. Click OK.