ApsaraDB RDS:Create a serverless ApsaraDB RDS for SQL Server instance

Prerequisites

Before you begin, ensure that you have:

• The AliyunRDSFullAccess RAM policy attached to the RAM user you use to create the instance. For more information, see Use RAM for resource authorization

Billing

A serverless ApsaraDB RDS for SQL Server instance is billed based on two components:

• RDS Capacity Units (RCUs): Charged based on actual RCU consumption within the configured scaling range.

• Storage: Charged based on the total storage capacity selected at creation, regardless of actual usage.

For pricing details, see Pricing of serverless ApsaraDB RDS for SQL Server instances.

Create an instance

1. Go to the ApsaraDB RDS buy page and set Billing Method to Serverless.

2. Select a Region. Serverless RDS instances are supported in the China (Hong Kong) and Singapore regions.

   Deploy the RDS instance in the same region as your application to enable internal network communication. If the RDS instance and your ECS instance are in different regions, they cannot communicate over an internal network. You cannot change the region after the instance is created.

3. Configure the database engine and compute parameters.

   Parameter	Description	Example
   Database engine	Select SQL Server and choose a version. Supported versions: SQL Server 2016 SE, SQL Server 2017 SE, and SQL Server 2019 SE.	2019 SE
   Edition	Fixed as High-availability Edition. Serverless instances support only this edition.	High-availability Edition
   Storage type	Fixed as PL1 ESSD. Serverless instances support only PL1 ESSDs. For more information, see Storage types.	PL1 ESSD
   RDS Capacity Units (RCUs)	Set the Minimum and Maximum RCU values. The system automatically scales RCUs within this range based on actual workloads. 1 RCU = 1 CPU core + 2 GB of memory. Minimum value: 2 RCUs. Maximum value: 16 RCUs.	Minimum: 2 RCUs, Maximum: 16 RCUs

4. Configure the network. Network Type is fixed as VPC (Virtual Private Cloud).

   1. Select a VPC. Deploy the RDS instance in the same VPC as your ECS instance to enable internal network communication. Instances in different VPCs cannot communicate over an internal network, even within the same region.

      Note: RDS instances and ECS instances in the same VPC but different vSwitches can still communicate over an internal network.

   2. Set Add to Whitelist to specify whether to add the CIDR block of the selected VPC to the IP address whitelist of the RDS instance.

      • Yes: ECS instances in the selected VPC can access the RDS instance immediately after creation.

      • No: Configure an IP address whitelist after the instance is created.

5. Select a zone, vSwitch, and deployment method.

   • Zone: Deploy the RDS instance in the same zone as your ECS instance for optimal performance. Instances in different zones within the same region have slightly higher latency.

   • vSwitch: Select an existing vSwitch or click Create vSwitch to create one. For more information, see Create and manage vSwitches.

   • Deployment Method: Choose how the primary and secondary instances are distributed across zones.

     Deployment method	Description
     Multi-zone Deployment (recommended)	The primary and secondary instances reside in different zones, providing cross-zone disaster recovery. Configure Zone And Network Of Primary Node and Zone And Network Of Secondary Node.
     Single-zone Deployment	The primary and secondary instances reside in the same zone.

   If a zone shows Sold Out, it has insufficient resources. Select a different zone.

6. Set Storage Capacity. Drag the slider to select the storage capacity. You are charged for the total capacity selected, not actual usage. For example, if you select 100 GB, you are billed for 100 GB even if usage is lower.

   After creation, you can expand the storage capacity, but you cannot reduce it. Charges update to reflect the new capacity after expansion.

7. (Optional) Configure additional settings. Keep the default values unless you have specific requirements.

   Parameter	Description
   Release Protection	Enable release protection to prevent accidental instance deletion.
   Resource Group	Select a resource group to organize and manage your instances.
   Instance Name	Enter a name. Length: 2–255 characters. Allowed characters: letters, digits, underscores (_), and hyphens (-). Must start with a letter.
   Privileged Account	Select Configure Now to create a privileged account by entering a Database Account and Password. Or select Configure Later to create an account after the instance is created. Each instance supports only one privileged account, which cannot be deleted.

8. In the upper-right corner, set Quantity (default: 1, maximum: 20), review the order details, click Confirm Order, and complete the payment.

9. Go to the Instances page. In the top navigation bar, select the region where you created the instance, then find the instance by Creation Time.

   If the instance fails to create due to insufficient resources in the selected zone, select a different zone and try again.

What's next

After creating the instance, complete these steps to make it ready for use:

• Create databases and accounts

• Configure an IP address whitelist

• Apply for or release a public endpoint

• Connect to an SQL Server instance

FAQ

How do I view the total number of RDS instances in my Alibaba Cloud account?

Log on to the ApsaraDB RDS console and go to the Overview page. The page shows the total number of instances by database engine, the regions where instances are deployed, and the number of running instances in each region.

Why can't I find an instance after creating it?

Check the following:

References

• Change the scaling range of RCUs for a serverless RDS for SQL Server instance

• Expand storage capacity for an RDS instance

• Release or unsubscribe from an RDS for SQL Server instance

• API: CreateDBInstance