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

Prerequisites

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

Billing

The fee for a serverless ApsaraDB RDS for SQL Server instance consists of the fees for RDS Capacity Units (RCUs) and fees for storage resources.

Procedure

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

2. Configure the Region parameter.

   Select the region in which you want to create the RDS instance. Serverless RDS instances can be created in the China (Hong Kong) and Singapore regions.

   Note

   • If your application or client is deployed on an ECS instance, we recommend that you set this parameter to the region in which the ECS instance resides. If the RDS instance and the ECS instance reside in different regions, these instances cannot communicate over an internal network. As a result, these instances cannot deliver optimal performance. You cannot change the region after the RDS instance is created.

   • If your application is deployed on an on-premises server or computer, we recommend that you select a region that is in close proximity to the on-premises server or computer. This way, you can use the public endpoint of the RDS instance to connect to the RDS instance from your application.

3. Configure the Database Engine, Edition, Storage Type, and RDS Capacity Units (RCUs) parameters.

   Parameter	Description	Example
   Database Engine	Set the value to Database Engine and select an engine version. SQL Server 2016 SE, SQL Server 2017 SE, and SQL Server 2019 SE are supported.	2019 SE
   Edition	Set the value to High-availability Edition. Serverless RDS instances run only RDS High-availability Edition.	High-availability Edition
   Storage Type	Set the value to PL1 ESSD. Serverless RDS instances support only ESSDs of PL1. For more information about storage types, see Storage types.	PL1 ESSD
   RDS Capacity Units (RCUs)	The performance of an RCU is equivalent to the performance of an RDS instance that has 1 CPU core and 2 GB of memory. The minimum value of the Minimum field is 2. The maximum value of the Maximum field is 16. After you configure the Minimum and Maximum parameters, the system automatically scales the RCUs of the serverless RDS instance within the range specified by the parameters based on the actual workloads.	Minimum: 2 RCUs Maximum: 16 RCUs

4. Configure the Network Type parameter. The Network Type parameter is fixed as VPC.

   1. Configure the VPC parameter.

      We recommend that you select the VPC in which your ECS instance resides for the RDS instance. If the RDS instance and the ECS instance reside in different VPCs, these instances cannot communicate over an internal network.

      Note

      You can connect the RDS instance and the ECS instance over an internal network even if the instances use different vSwitches in the same VPC.

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

      If you set this parameter to Yes, the ECS instances that reside in the selected VPC can access the RDS instance.

      Note

      If you set this parameter to No, you can configure an IP address whitelist after the RDS instance is created.

5. Select a zone and vSwitch and then configure the Deployment Method parameter.

   • Select a zone

     A zone is an independent physical location within a region. For example, the China (Hangzhou) region contains Zone H, Zone I, and Zone J.

     • All zones in a region provide the same services.

     • If the RDS instance resides in the same zone as the ECS instance on which your application is deployed, these instances can deliver optimal performance. If the RDS instance and the ECS instance reside in different zones in the same region, the performance of the RDS instance and the ECS instance is slightly lower than the performance of the RDS instance and the ECS instance that reside in the same zone.

   • Select a vSwitch

     A vSwitch is a basic network device that connects different cloud resources. When you create a cloud resource in a VPC, you must specify a vSwitch to which the cloud resource is connected.

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

   • Select a deployment method

     • Multi-zone Deployment (recommended): The primary RDS instance and the secondary RDS instance reside in different zones to achieve cross-zone disaster recovery.

       If you set the Deployment Method parameter to Multi-zone Deployment, you must configure the Zone And Network Of Primary Node and Zone And Network Of Secondary Node parameters.

     • Single-zone Deployment: The primary RDS instance and the secondary RDS instance reside in the same zone.

       If you select RDS Basic Edition, you can select only the Single-zone Deployment method.

     Note

     • If your database system consists of primary and secondary RDS instances, we recommend that you select Multi-zone Deployment to implement cross-zone disaster recovery.

     • If Sold Out appears in the upper-right corner of a zone name, this zone does not have sufficient resources. Switch to another zone.

6. Configure the Storage Capacity parameter.

   Drag the slider to adjust the storage capacity. You are charged for the total storage capacity that you select when you create a serverless RDS instance. For example, if you select 100 GB of storage capacity when you create the serverless RDS instance, you are charged based on 100 GB even if the storage usage is less than 100 GB.

   Note

   If the storage capacity cannot meet your business requirements, you can manually expand the storage capacity. After the storage capacity is expanded, the storage capacity cannot be reduced, and you are charged based on the new storage capacity.

7. Configure custom parameters. If you do not have special business requirements, you can retain the default values of these parameters.

   Parameter	Description
   Release Protection	You can enable the release protection feature for the instance to prevent the instance from being released due to unintended operations.
   Resource Group	You can use the default resource group or select a custom resource group as needed. This facilitates instance management.
   Instance Name	The value must be 2 to 255 characters in length and can contain letters, digits, underscores (_), and hyphens (-). It must start with a letter.
   Privileged Account	You can select Configure Now and configure the Database Account and Password parameters to create a privileged account when you create the RDS instance. You can also click Configure Later and create a privileged account after the RDS instance is created. Important Each RDS instance can have only one privileged account. The privileged account cannot be deleted.

8. In the upper-right corner of the page, configure the Quantity parameter.

   The default value is 1. You can purchase up to 20 instances at a time. Specify the number of instances as needed.

9. In the right side of the page, confirm the order information and the quantity, click Confirm Order, and then complete the payment.

10. View the RDS instance.

    Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance based on the Creation Time parameter.

    Note

    An RDS instance may fail to be created because of insufficient resources in the specified zone. In this case, select a different zone and try again.

What to do next

• Create databases and accounts

• Configure an IP address whitelist

• Apply for or release a public endpoint

• Connect to an SQL Server instance

FAQ

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

• Call an API operation to create a serverless RDS for SQL Server instance: CreateDBInstance