This topic describes how to upgrade an RDS for SQL Server instance from the 2008 R2 version to the 2012 or 2016 version. During the upgrade, you can also migrate the instance to other zones. We recommend that you use a temporary instance of the target version to test the version compatibility before the upgrade.

Prerequisites

  • The storage capacity of your SQL Server 2008 R2 instance is at least 20 GB.
  • The TDE feature of your SQL Server 2008 R2 instance has not been enabled.
    Note If TDE is enabled, you must disable TDE for all databases and then open a ticket to disable TDE for the entire instance.

Precautions

  • Your instance cannot be rolled back to SQL Server 2008 R2 after the upgrade is completed.
    Warning We recommend that you use a temporary instance of the target version to test the version compatibility before the upgrade.
  • You can upgrade from SQL Server 2008 R2 to SQL Server 2012/2016 Enterprise Edition or SQL Server 2016 Standard Edition only.
  • If SSL is enabled for your instance, you can still upgrade your instance version directly. After the upgrade is completed, the instance connection address remains unchanged, but SSL is disabled by default. You can enable it again by referring to Configure SSL encryption.
  • The TDE feature remains if you upgrade your instance from SQL Server 2008 R2 to SQL Server 2012/2016 Enterprise Edition, but does not exist if you upgrade your instance to SQL Server 2016 Standard Edition.
  • After the upgrade is completed, the downtime caused by the backend switchover depends on the instance size. The switchover is usually completed within 20 minutes. We recommend that you choose the maintenance window as the swithover time and make sure that your applications can automatically reconnect to the instance.

Procedure

  1. Log on to the RDS console.
  2. Select the region where your instance is located.
    Select a region
  3. Click the ID of your instance.
  4. On the Basic Information page, click Upgrade Version. In the displayed dialog box, click Confirm.
    Upgrade the database version
  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 Type settings vary depending on the selected target version.
    Edition Select High-availability: The classic HA architecture allows your instance to work in master/slave mode with balanced performance in all aspects.
    Storage Type Select SSD or ESSD.
    Zone Select the zone to which you want to migrate your instance. You can choose a multi-zone combination if available.
    Type Each instance type provides 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 the original network type is the classic network, you can select any VPC and vSwitch.
    • If the original network type is a VPC or the hybrid mode (both classic network and a VPC), you cannot change the VPC but you can change the VSwitch. The available VSwitches vary depending on the specified Zone and VPC.
    VSwitch Select the VSwitch. If you select multiple zones for your instance, you need to select multiple VSwitches.
    Switching Time
    • Switch Immediately After Data Migration: After the data migration, the switchover occurs immediately.
    • Switch Within Maintenance Window: After the data migration, the switchover does not occur until the maintenance period.

    升级引擎版本页面
  6. Select the terms of service and click Confirm.

Instance connection address after the upgrade

After the upgrade, the instance connection address is changed as follows.

If the original network type is Then after the upgrade
Classic network Two connection addresses are available:
  • The original connection address of the classic network still can be used and will not expire.
  • A VPC connection address is generated for the instance based on the VPC that is specified during the upgrade.
VPC A new VPC connection address is generated based on the VPC that is specified during the upgrade. This address replaces the original VPC connection address of the instance.
Hybrid mode (Classic network and VPC) The instance remains in hybrid mode. The original classic network and VPC connection addresses remain unchanged. The expiration time of the classic network connection address also 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 RDS console.
  2. Select the region where your instance is located.
  3. Click the ID of your instance.
  4. In the left-side navigation pane, click Backup and Restoration.
  5. Click the Temporary Instance tab, specify the time from which you want to clone data, and click Create Temporary Instance of Higher Version.
    Select a temporary instance of the target version
  6. In the displayed dialog box, set the following parameters.
    Parameter Description
    Zone Select the zone where you can create a temporary instance.
    Upgrade To Version Select the target version. The available target versions are as follows:
    • 2016 SE
    • 2016 EE
    • 2012 EE
    VPC Select the VPC where the ECS instance to be connected is located. Otherwise, the temporary instance cannot communicate with the ECS instance through the intranet.
    VSwitch Select a VSwitch under the specified VPC.
    Note The temporary instance adopts a default instance type and a default storage type.

    Temporary instance of the target version
  7. Click OK.
    Note The temporary instance will be automatically released after seven days.

Related API

API Description
UpgradeDBInstanceEngineVersion Upgrades the database version of an instance.