This topic provides an overview of ApsaraDB RDS for SQL Server and describes the related terms.
Disclaimer
Some features or capabilities that are described in this topic may be unavailable. The specific terms and conditions in your commercial contract shall prevail. This topic serves as a user guide that is for reference only. Content in this topic is provided without warranty of any kind, expressed or implied.
RDS SQL Server
ApsaraDB RDS supports the SQL Server database engine. ApsaraDB RDS for SQL Server is built on top of a high-availability architecture and supports the restoration of data to a specific point in time. These highlights enable ApsaraDB RDS for SQL Server to support various enterprise applications. In addition, ApsaraDB RDS for SQL Server includes Microsoft-issued licenses.
The license for an ApsaraDB RDS for SQL Server instance is approved based on the number of cores that are configured for the RDS instance. You do not need to obtain a client access license.
ApsaraDB RDS for SQL Server provides the following advanced features:
ApsaraDB for MyBase dedicated clusters: An ApsaraDB for MyBase dedicated cluster consists of multiple hosts, such as Elastic Compute Service (ECS) instances of the ecs.i2.xlarge instance type and ECS Bare Metal instances. You can deploy RDS instances on these hosts based on your varying business requirements. For more information, see What is ApsaraDB for MyBase?
Cloud disk encryption: This feature encrypts the entire data disks of your RDS instance based on block storage. Your data cannot be accessed even if data leaks occur. For more information, see Configure disk encryption for an ApsaraDB RDS for SQL Server instance. Cloud disk encryption does not interrupt your workloads. In addition, you do not need to modify your application configurations.
Read-only RDS instances: If the primary RDS instance is overwhelmed by a large number of read requests, your workloads may be interrupted. In this case, you can create one or more read-only RDS instances to offload read requests from the primary RDS instance. For more information, see Create a read-only ApsaraDB RDS for PostgreSQL instance. Read-only RDS instances help increase the read capability of your database system and the throughput of your application.
Read/write splitting: After read-only RDS instances are created, you can enable the read-only routing endpoint and add the endpoint of the primary RDS instance and the read-only routing endpoint to your application. Your database system forwards write requests to the primary RDS instance and read requests to the read-only routing endpoint. Then, the read-only routing endpoint forwards the read requests to the read-only RDS instances based on the read weights of the read-only RDS instances. For more information, see Overview of read/write splitting.
For more information about the features that are supported by ApsaraDB RDS for SQL Server, see Features.
To manage complex business, you can purchase a support plan to request support from enterprise instant messaging (IM) groups, technical account managers (TAMs), and service managers.
For more information about ApsaraDB RDS for SQL Server, visit the ApsaraDB RDS for SQL Server product page.
Terms
instance: An RDS instance is a database process that consumes independent physical memory resources. You can specify a specific memory size, storage capacity, and database type for an RDS instance. The performance of an RDS instance varies based on the specified memory size. After an RDS instance is created, you can change its specifications or delete the instance.
database: A database is a logical unit that is created on an RDS instance. One RDS instance can have multiple databases. Each database must have a unique name on the RDS instance on which the database is created.
region and zone: Each region is a physical data center. Each region has multiple isolated locations known as zones. Each zone has its own independent power supply and networks. For more information, see Global infrastructure of Alibaba Cloud.
General terms
Term | Description |
on-premises database | A database that is deployed in a data center or a database that is not deployed on an ApsaraDB RDS instance. |
ApsaraDB RDS for XX (XX represents one of the following database engines: MySQL, SQL Server, PostgreSQL, and MariaDB.) | ApsaraDB RDS with a specific database engine. For example, ApsaraDB RDS for MySQL indicates an ApsaraDB RDS instance that runs MySQL. |