All Products
Search
Document Center

ApsaraDB RDS:Update the minor engine version of an ApsaraDB RDS for SQL Server instance

Last Updated:Oct 25, 2023

This topic describes how to update the minor engine version of an ApsaraDB RDS for SQL Server instance. These updates are used to enhance database performance, introduce new features, and fix bugs.

For more information about the release notes for minor engine versions of ApsaraDB RDS for SQL Server, see Release notes for minor engine versions of ApsaraDB RDS for SQL Server.

For more information about how to update the minor engine version of an RDS instance that runs a different database engine, see the following topics:

Prerequisites

The RDS instance meets the following requirements:

  • The RDS instance runs RDS Basic Edition, RDS High-availability Edition, or RDS Cluster Edition. Serverless RDS instances are not supported.

  • The RDS instance uses a general-purpose or dedicated instance type. Shared instance types are not supported.

Note

Usage notes

  • An update requires several hours to several days based on the data volume of your RDS instance.

  • During the update, a transient connection that lasts approximately 20 to 30 minutes occurs. We recommend that you perform the update during off-peak hours. In addition, make sure that your application is configured to automatically reconnect to your RDS instance. If the write workload is heavy during the update, a longer period of time is required to complete the update.

  • After you update the minor engine version of your RDS instance, you cannot roll the minor engine version of the RDS instance back to the previous version.

    Warning

    Before you perform an update, we recommend that you create an RDS instance that runs the required minor engine version to test overall compatibility. For more information, see Restore the data of an ApsaraDB RDS for SQL Server instance.

  • After you update the minor engine version of your RDS instance, the value of the Backup Size parameter on the Basic Information page of your RDS instance may be displayed as 0. After the next scheduled backup is complete, this error is automatically fixed.

  • In most cases, minor engine version updates do not cause compatibility issues. However, minor engine version updates may cause changes in functionality. We recommend that you check SQL Server CUs released by Microsoft to check whether the SQL Server kernel is updated.

  • During the upgrade, we recommend that you do not modify metadata of your RDS instance. Otherwise, data inconsistency issues may occur after the upgrade. For example, we recommend that you do not create databases, delete databases, or modify the recovery models of databases.

Limits

You cannot update the minor engine version of the following RDS instances:

View the minor engine version of your RDS instance

You can use one of the following methods to view the minor engine version of your RDS instance:

Update the minor engine version of your RDS instance

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
  2. In the Configuration Information section of the page that appears, click Upgrade Minor Engine Version.

    Note

    If you cannot find Update Minor Engine Version, the minor engine version of your RDS instance is the latest version or your RDS instance does not meet the requirements that are described in Prerequisites.

  3. In the dialog box that appears, configure the Available Upgrade and Upgrade Time parameters and click OK.

    升级小版本

Related operations

Operation

Description

UpgradeDBInstanceKernelVersion

Updates the minor engine version of an instance.