This topic describes how to change the specifications of an ApsaraDB RDS for SQL Server instance. These specifications include the RDS edition, instance type, storage capacity, storage type, and zone.

Prerequisites

Your Alibaba Cloud account does not have overdue renewal orders.

Note You cannot directly upgrade an RDS instance from a shared instance type to a general-purpose or dedicated instance type. However, this function is in development. You can create an RDS instance that is designed to use a specific general-purpose or dedicated instance type and then use Alibaba Cloud Data Transmission Service (DTS) to migrate data to the new RDS instance. For more information, see Data migration solutions.

Change items

You can create read-only RDS instances to scale the read capability of your database system. These instances can offload queries from the primary RDS instance. For more information, see Overview of read-only ApsaraDB RDS for SQL Server instances and Create a read-only ApsaraDB RDS for SQL Server instance.
Change item Description
Database engine version Some versions can be upgraded to later versions. For more information, see the following topics:
RDS edition You can upgrade an RDS instance from the RDS Basic to High-availability Editions. For more information, see Upgrade from Basic Edition to High-availability Edition.
Instance type You can change the instance types of all RDS instances.
Storage type
  • You can upgrade the storage type of an RDS instance from standard SSD to enhanced SSD. This applies when the RDS instance runs SQL Server 2012 or 2016 on RDS High-availability Edition. However, you cannot downgrade the instance type from enhanced SSD to standard SSD.
  • You can change the performance levels (PLs) of all RDS instances that are equipped with enhanced SSDs.
Storage capacity You can increase the storage capacity of all RDS instances.
Note
  • You cannot decrease the storage capacity.
  • The new storage capacity that you specify must fall within the storage capacity range allowed for the instance type. For more information, see Primary instance types.
  • The storage capacity of a primary RDS instance must be greater than or equal to that of its read-only RDS instance. If a primary RDS instance has a read-only RDS instance, you must increase the storage capacity of the read-only RDS instance before you can increase the storage capacity of the primary RDS instance.
  • If the storage capacity range allowed for the instance type that you are using cannot meet your business requirements, we recommend that you select another instance type.
Note Changing the preceding specifications of an RDS instance does not incur changes to the endpoints of the RDS instance.

Billing

For more information, see Specification change fees.

Precautions

  • Data may be migrated after you change the specifications of an RDS instance. After the migration is complete, the RDS instance switches over services during the scheduled time period. The switchover does not interrupt the synchronization of incremental data. During a switchover, a 30-second brief disconnection may occur. In addition, operations related to databases, accounts, and networks cannot be performed. We recommend that you change the specifications during off-peak hours or make sure that your application is configured to automatically reconnect to your RDS instance.
  • After you change the specifications of an RDS instance, you do not need to manually restart the RDS instance.
  • In the RDS Basic Edition, the database system consists of only one primary RDS instance, and no secondary RDS instances are provided as hot backups. If the primary RDS instance breaks down, is undergoing specification changes, or is upgrading, it becomes unavailable until the operations are done. If you require high database availability, we recommend that you use the RDS High-availability, Cluster, or Enterprise Edition.

Procedure

  1. Log on to the ApsaraDB for RDS console.
  2. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where the target RDS instance resides.
    Select a region
  3. Find the target instance and click the instance ID.
  4. Click Change Specifications.
  5. In the dialog box that appears, select a change method and click Next. This step is required only for subscription instances.
    Note You can select Upgrade or Downgrade for both subscription and pay-as-you-go instances. The new specifications immediately take effect.
  6. Change the specifications of the RDS instance. For more information, see Change items.
  7. Specify the Switching Time.
    • Switch Immediately After Data Migration: The system executes the specification changes immediately after data migration is complete.
    • Switch Within Maintenance Window: The system executes the specification changes during the maintenance window that you specify.
  8. On the Change Specifications page, read and select Terms of Service, and click Pay Now.

FAQ

  1. Can I change the zone and database engine version of my ApsaraDB RDS for SQL Server instance?

    Only SQL Server 2008 R2 that is used with local SSDs allows you to change the zone and database engine version. You can change the zone separately. You can also change the zone while you upgrade the database engine version.

  2. If I only want to increase the storage capacity of my ApsaraDB RDS for SQL Server instance, do I need to migrate the data of the instance to a new instance?

    No, you only need to increase the storage capacity of your ApsaraDB RDS for SQL Server instance. You do not need to manually migrate the data. When you increase the storage capacity, the system checks whether the host where the instance resides can provide sufficient storage capacity. If yes, the system increases the storage capacity without migrating the data. If no, the system migrates the data to a new instance before increasing the storage capacity. The new instance must be created on a host that provides sufficient storage capacity.

Related operations

Operation Description
ModifyDBInstanceSpec Changes the specifications of an RDS instance.