This topic describes how to upgrade a local SSD-based instance from SQL Server 2008 R2 to SQL Server 2012 or 2016. During the upgrade, you can also migrate the instance to other zones.

Alibaba Cloud has stopped providing security updates for ApsaraDB RDS for SQL Server 2008 R2 instances purchased on and after July 9, 2019. For more information, see Supplementary service agreement. We recommend that you upgrade your version as soon as possible.

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

Billing

For information about the billing for version upgrade, see Specification change fees.

Impact

After you complete the upgrade, you must switch services over. The downtime caused by the switchover varies by instance type. Typically, it takes about 20 minutes to complete switchover. We recommend that you switch services over during a maintenance window and make sure that your applications are configured with automatic reconnection policies.

Prerequisites

  • The instance runs SQL Server 2008 R2 with local SSDs.
  • The total storage capacity of the instance is at least 20 GB.
  • The TDE feature is disabled for the instance.
    Note If TDE is enabled, you must disable the TDE feature for all databases and then submit a ticket to request to disable TDE for the instance.

Precautions

  • Your instance cannot be rolled back to SQL Server 2008 R2 after an upgrade is complete.
    Warning We recommend that you use a temporary instance of the target version to test version compatibility before you proceed with an upgrade.
  • You can upgrade a local SSD-based instance 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 instance, you can upgrade your instance version directly. After the upgrade is complete, the instance endpoint remains unchanged, but SSL is disabled by default. You must re-enable SSL. For more information, see Configure SSL encryption for an RDS instance.
  • The TDE feature remains after you upgrade your local SSD-based instance from SQL Server 2008 R2 to SQL Server 2012 or 2016 EE. However, TDE will be disabled if you upgrade your instance to SQL Server 2016 SE.

Procedure

  1. Log on to the ApsaraDB for RDS console.
  2. Select the region where the instance is located.Select a region
  3. Click the ID of the instance.
  4. On the Basic Information page, click Upgrade Version. In the message that appears, click OK.Upgrade the database engine version
  5. On the Upgrade Engine Version page, configure the following parameters.
    Parameter Description
    Upgrade To Select the target version. The available Edition, Storage Type, and CPU and Memory 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 implement balanced performance in all aspects.
    Storage Type
    • Standard SSD: an elastic block storage device based on the distributed storage architecture. If you use standard SSDs, computing is separated from storage.
    • Enhanced SSD: an ultra-high performance cloud disk provided by Alibaba Cloud. Enhanced SSDs (ESSDs) are based on the latest generation of distributed block storage architecture. With 25 Gigabit Ethernet and remote direct memory access (RDMA) technologies, this architecture provides several benefits. These benefits include low latency for single-line communication and up to one million random input/output operations per second (IOPS) for a single disk.
    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 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 instance is accessed through the 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 the 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.
    VSwitch Select the target VSwitch. If you select multiple zones for your instance, you must select multiple target VSwitches.
    Note
    • If you select the default VPC, the target VSwitch can be either the default VSwitch or a non-default VSwitch.
    • If you do not select the default VPC, 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 window.
    Upgrade configuration
  6. Select the terms of service and click Confirm.

Change the connection endpoint

After the upgrade, the instance can only be accessed through a VPC. The following table describes how the connection endpoint changes 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 the classic network and a VPC:
  • The original connection endpoint of the classic network still applies to the instance after the upgrade. This endpoint does not expire.
  • A VPC connection endpoint is generated for the instance after the upgrade based on the VPC that is specified during the upgrade.
VPC A VPC connection endpoint is generated for the instance after the upgrade based on the VPC specified during the upgrade. This endpoint replaces the original VPC connection endpoint of the instance.
Classic network and VPC The instance after the upgrade is accessed still through both the classic network and a VPC. The original classic network and VPC connection endpoints still apply to the instance after the upgrade. The expiration time of the classic network connection endpoint remains unchanged.

Create a temporary instance of the target version

Before the upgrade, we recommend that you create a temporary instance of the target version to test the version compatibility.

Note You can create a temporary instance of the target version only for an SQL Server 2008 R2 instance whose TDE and SSL are disabled.
  1. Log on to the ApsaraDB for RDS console.
  2. Select the region where the instance is located.
  3. Click the ID of the instance.
  4. In the left-side navigation pane, click Backup and Restoration.
  5. On the Temporary Instance tab, specify the time at which you want to clone data, and click Create Temporary Instance of Higher Version.Select a temporary instance of the target version
  6. Configure the following parameters.
    Parameter Description
    Zone Select the zone in which to create a temporary instance.
    Upgrade To Select the target version. The available target versions are as follows:
    • 2016 SE
    • 2016 EE
    • 2012 EE
    VPC Select a VPC. You must select the VPC where the ECS instance to be connected is located. Otherwise, the temporary instance cannot communicate with the ECS instance through the internal network.
    VSwitch Select a VSwitch from the specified VPC.
    Note The system provides a default instance type and storage type for temporary instances. The temporary instance will be automatically released after seven days.
    Temporary instance of the target version
  7. Click OK.