RDS editions of ApsaraDB RDS for SQL Server and the scenarios of each RDS edition - ApsaraDB RDS

This topic describes the RDS editions of ApsaraDB RDS for SQL Server and the scenarios, supported instance types, and features of each RDS edition.

Description of RDS editions of ApsaraDB RDS for SQL Server

RDS edition	Description	Scenario
RDS Basic Edition	The database system consists of only one primary RDS instance. Computing is separated from storage. Read-only RDS instances are not supported.	Personal learning Microsites Development and testing environments for small and medium-sized enterprises
RDS High-availability Edition	The database system consists of a primary RDS instance and a secondary RDS instance. These instances work in high availability (HA) mode and support automatic failover. The secondary RDS instance cannot be accessed. Read-only RDS instances are not supported.	Production databases for large and medium-sized enterprises Databases that are used in industries such as the Internet, IoT, e-commerce, logistics, and gaming
RDS Cluster Edition	The database system consists of a primary RDS instance and a secondary RDS instance. These instances work in HA mode and support automatic failover. The secondary RDS instances can be accessed. This increases the read capability of your database system. You can create up to seven read-only RDS instances to improve the read capability. However, read-only RDS instances do not participate in the primary instance election or workload switchover. For more information, see Create a read-only ApsaraDB RDS for SQL Server instance.	Production databases for large and medium-sized enterprises Databases that are used in industries such as Internet-based new retail and automobile manufacturing, and databases that are used for ERP systems

Change the RDS edition of an RDS instance

If your RDS instance runs one of the following database engine versions, you can upgrade the RDS instance from RDS Basic Edition to RDS High-availability Edition. For more information, see Upgrade the major engine version.
- SQL Server 2022 SE, SQL Server 2019 SE, SQL Server 2017 SE, SQL Server 2016 SE, and SQL Server 2014 SE
- SQL Server 2022 Web, SQL Server 2019 Web, SQL Server 2017 Web, SQL Server 2016 Web, and SQL Server 2012 Web
- SQL Server 2016 EE and SQL Server 2012 EE Basic
If your RDS instance runs one of the following database engine versions, you can upgrade the RDS instance from RDS High-availability Edition to RDS Cluster Edition. For more information, see Upgrade the major engine version.
- SQL Server 2022 SE, SQL Server 2019 SE, SQL Server 2017 SE, SQL Server 2016 SE, SQL Server 2014 SE, and SQL Server 2012 SE
- SQL Server 2016 EE, SQL Server 2014 EE, and SQL Server 2012 EE

Note

You cannot change the RDS edition of an RDS instance that does not meet the requirements in the preceding list. If you want to change the RDS edition of the RDS instance, you must create an RDS instance that runs the specified RDS edition and then migrate the data of the original RDS instance to the new RDS instance. For more information, see Create an ApsaraDB RDS for PostgreSQL instance and Migrate data between ApsaraDB RDS for PostgreSQL instances.

View the RDS edition of an RDS instance

You can log on to the ApsaraDB RDS console, find the RDS instance, and then go to the Basic Information page to view the edition of the RDS instance.

Instance types supported by various RDS editions

For more information, see Instance types for primary ApsaraDB RDS for SQL Server instances.

Features supported by various RDS editions

For more information, see Features.

Create an RDS instance

For more information, see Create an ApsaraDB RDS for SQL Server instance.