This topic describes how to create an ApsaraDB RDS for SQL Server instance in the ApsaraDB for RDS console. You can also call an API operation to create an ApsaraDB RDS for SQL Server instance.

For more information about how to create an ApsaraDB RDS for SQL Server instance by calling an API operation, see CreateDBInstance.

For more information about the billing of ApsaraDB RDS for SQL Server instances, see Pricing, billing items, and billing methods.

A new ApsaraDB for RDS console is available for instance creation. You can choose the new console or switch back to the original console. For more information, see the following sections:

Prerequisites

You have an Alibaba Cloud account. For more information, see Sign up with Alibaba Cloud.

Precautions

Create an RDS instance in the new ApsaraDB for RDS console

  1. Log on to the new ApsaraDB for RDS console.
    Note You can click Back to Old Version in the upper-right corner to switch back to the original ApsaraDB for RDS console.
  2. Configure the following parameters.
    Parameter Description
    Billing Method
    • Subscription: A subscription instance is an instance that you subscribe to for a period of time and pay for up front. We recommend that you choose subscription billing for long-term use because it is more cost-effective than pay-as-you-go billing. You can receive larger discounts for longer subscription periods.
    • Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. We recommend that you choose pay-as-you-go billing for short-term use. You can release your pay-as-you-go instance to reduce costs when you no longer need it.
    Region The region where the RDS instance resides.
    • You cannot change the region after you confirm your order.
    • To maximize access speed, we recommend that you select a region in close proximity to the geographic location where your users reside.
    • Make sure that the RDS instance is created in the same region as the ECS instance to which you want to connect. If the RDS and ECS instances reside in different regions, they cannot communicate over an internal network and therefore cannot deliver optimal performance.
    Database Engine The database engine and version that the RDS instance runs. Select the Microsoft SQL Server database engine. Supported SQL Server versions are 2008 R2, 2012, 2014, 2016, 2017, and 2019.
    Note The database engines and versions available vary based on the region you select.
    Edition
    • Basic: Your database system consists of only one instance. Computing is separated from storage to increase cost-effectiveness.
    • High-availability: Your database system consists of one primary instance and one secondary instance. The primary and secondary instances work in the classic high-availability architecture.
    • AlwaysOn: Your database system consists of one primary instance, one secondary instance, and up to seven read-only instances that are created to process more read requests.
    Note The RDS editions available vary based on the region and database engine version you select. For more information, see ApsaraDB for RDS edition overview.
    Storage Type
    • Local SSD: A local SSD is housed on the same server as the database engine. Local SSDs reduce I/O latency.
    • Enhanced SSD: An enhanced SSD is an ultra-high performance disk provided by Alibaba Cloud based on the new generation of distributed block storage architecture. It integrates 25 Gigabit Ethernet and remote direct memory access (RDMA) technologies to reduce latency and deliver up to 1 million random input/output operations per second (IOPS). Enhanced SSDs are available in the following three performance levels (PLs):
      • Enhanced SSD: This is an enhanced SSD of PL1.
      • ESSD PL2: An enhanced SSD of PL2 delivers an IOPS and throughput that are twice as high as those delivered by an enhanced SSD of PL1.
      • ESSD PL3: An enhanced SSD of PL3 delivers an IOPS that is 20 times as high as the IOPS delivered by an enhanced SSD of PL1. It also delivers throughput that is 11 times as high as the throughput delivered by an enhanced SSD of PL1. Enhanced SSDs of PL3 are ideal for businesses that require high I/O performance in processing concurrent requests and stable read/write latency.
    • Standard SSD: A standard SSD is an elastic block storage device that is designed based on the distributed storage architecture. Standard SSDs separate computing from storage.

    For more information, see Storage types.

    Note Both standard and enhanced SSDs support the Disk Encryption option. You can select this option to enable disk encryption. Disk encryption ensures the security of your data without the need to change business or application configurations. For more information, see Configure disk encryption.
    Zone of Primary Node

    The zone of primary node where the RDS instance resides. Each zone is an independent physical location within a region. There is no substantive difference between zones in the same region. If your database system spans multiple zones, it provides zone-level disaster recovery.

    You only need to select a primary zone. The system automatically assigns a secondary zone to the RDS instance.

    Deployment Method You can set the instance as multi-zone or single-zone deployment.
    Instance Type
    • Entry-level: belongs to the general-purpose instance family. A general-purpose instance exclusively occupies the memory and I/O resources allocated to it, but shares CPU and storage resources with the other general-purpose instances that are deployed on the same server.
    • Enterprise-level: belongs to the dedicated or dedicated host instance family. A dedicated instance exclusively occupies the CPU, memory, storage, and I/O resources allocated to it. The top configuration of the dedicated instance family is the dedicated host. A dedicated host instance occupies all the CPU, memory, storage, and I/O resources on the server where it is housed.
    Note Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary instance types.
    Capacity The storage capacity that the RDS instance has available to store data files, system files, binary log files, and transaction files. You can adjust the storage capacity in increments of 5 GB.
    Note The dedicated instance family supports exclusive allocations of resources. The storage capacity of each instance type with local SSDs in this family is fixed. For more information, see Primary instance types.
  3. Click Next: System Configurations.
  4. Configure the following parameters.
    Parameter Description
    Network Type
    • Classic Network: a traditional type of network.
    • VPC: A Virtual Private Cloud (VPC) is an isolated virtual network with higher security and better performance than a classic network. If you select the VPC network type, you must also specify VPC and VSwitch of Primary Node.
    Note Make sure that the primary RDS instance has the same network type as the ECS instance to which you want to connect. If both their network types are VPC, you must also make sure that they reside in the same VPC. Otherwise, they cannot communicate over an internal network.
  5. Click Next: Confirm Order. In the Confirm Order step, confirm the settings in the Parameters section, specify Purchase Plan and Duration, read and select Terms of Service, and click Pay Now. You need to specify Duration only when you create a subscription instance.

Create an RDS instance in the original ApsaraDB for RDS console

  1. Log on to the original ApsaraDB for RDS console.
  2. Select a billing method.
    • Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. We recommend that you choose pay-as-you-go billing for short-term use. You can release your pay-as-you-go instance to reduce costs when you no longer need it.
    • Subscription: A subscription instance is an instance that you subscribe to for a period of time and pay for up front. We recommend that you choose subscription billing for long-term use because it is more cost-effective than pay-as-you-go billing. You can receive larger discounts for longer subscription periods.
  3. Configure the following parameters.
    Parameter Description
    Region The region where the RDS instance resides. You cannot change the region after you confirm your order.
    • To maximize access speed, we recommend that you select a region in close proximity to the geographic location where your users reside.
    • Make sure that the RDS instance is created in the same region as the ECS instance to which you want to connect. If the RDS and ECS instances reside in different regions, they cannot communicate over an internal network and therefore cannot deliver optimal performance.
    Resource Group The resource group to which the RDS instance belongs.
    Database Engine

    The database engine that the RDS instance runs. Select the Microsoft SQL Server database engine.

    Note The database engines available vary based on the region you select.
    Version The SQL Server version that the RDS instance runs. Supported SQL Server versions are 2008 R2, 2012, 2016, 2017, and 2019. For more information, see Functions supported by different versions and editions of SQL Server.
    Note The database engine versions available vary based on the region you select.
    Edition
    • Basic: Your database system consists of only one instance. Computing is separated from storage to increase cost-effectiveness.
    • High-availability: Your database system consists of one primary instance and one secondary instance. The primary and secondary instances work in the classic high-availability architecture.
    • AlwaysOn: Your database system consists of one primary instance, one secondary instance, and up to seven read-only instances that are created to process more read requests.
    For more information, see ApsaraDB for RDS edition overview.

    The RDS editions available vary based on the database engine version you select.

    Storage Type
    • Local SSD: A local SSD is housed on the same server as the database engine. Local SSDs reduce I/O latency.
    • Standard SSD: A standard SSD is an elastic block storage device that is designed based on the distributed storage architecture. Standard SSDs separate computing from storage.
      Note Both standard and enhanced SSDs support the Disk Encryption option. You can select this option to enable disk encryption. Disk encryption ensures the security of your data without the need to change business or application configurations. For more information, see Configure disk encryption.
    • Enhanced SSD: An enhanced SSD is an ultra-high performance disk provided by Alibaba Cloud based on the new generation of distributed block storage architecture. It integrates 25 Gigabit Ethernet and RDMA technologies to reduce latency and deliver up to 1 million random IOPS.

    For more information, see Storage types.

    Key The key used for disk encryption. This parameter appears only when the Disk Encryption option is selected. For more information, see Manage CMKs.
    Zone

    The zone where the RDS instance resides. Each zone is an independent physical location within a region. There are no substantive differences between zones in the same region. You can create your primary and secondary instances in the same zone or in different zones.

    If your database system spans multiple zones, it provides zone-level disaster recovery.

    Network Type
    • Classic Network: a traditional type of network.
    • VPC: This is the recommended network type. A VPC is an isolated virtual network with higher security and better performance than a classic network.
      Note Make sure that the RDS instance has the same network type as the ECS instance to which you want to connect. If the RDS and ECS instances have different network types, they cannot communicate over an internal network.
    CPU and Memory The type of the RDS instance. Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary instance types.

    ApsaraDB RDS for SQL Server provides the following instance families:

    • General-purpose instance: A general-purpose instance exclusively occupies the memory and I/O resources allocated to it, but shares CPU and storage resources with the other general-purpose instances that are deployed on the same server.
    • Dedicated instance: A dedicated instance exclusively occupies the CPU, memory, storage, and I/O resources allocated to it.
    • Dedicated host: This is the top configuration of the dedicated instance family. A dedicated host instance occupies all the CPU, memory, storage, and I/O resources on the server where it is housed.

    For example, "8 Cores, 32 GB" is a general-purpose instance type, "8 Cores, 32 GB (Dedicated Instance)" is a dedicated instance type, and "30 Cores, 220 GB (Dedicated Host)" is a dedicated host instance type.

    Capacity The storage capacity that the RDS instance has available to store data files, system files, binary log files, and transaction files.
  4. Specify Duration and Quantity, and click Buy Now. You need to specify Duration only when you create a subscription instance.
    Note
    • When you create a subscription instance, you can select Auto-renewal. The system automatically renews your subscription based on the duration you specify. For example, if you create a three-month subscription instance with Auto-renewal selected, you are charged a three-month subscription fee for each automatic renewal.
    • When you create a subscription instance, you can click Add to Cart to add it to the shopping cart. Later, you can click Cart to pay for the subscription instance.
  5. On the Order Confirmation page, confirm the instance configuration, read and select Product Terms of Service, and click Pay Now.

What to do next

In the top navigation bar, select the region where the RDS instance you created resides.Select a region

After the RDS instance is created, you must configure whitelists and create accounts for it. If you want to connect to the RDS instance over the Internet, you must also apply for a public endpoint. For more information, see Apply for a public endpoint for an RDS SQL Server instance. Then you can connect to the RDS instance.

FAQ

  • After I purchase an RDS instance, the ApsaraDB for RDS console does not respond nor can I find the instance I just created. Why?

    There are two possible reasons:

    • The RDS instance you created does not reside in the region you selected.

      In the top navigation bar, select the region where the RDS instance resides. Then you can find the RDS instance you just created.

      Select a region
    • The zone you selected cannot provide sufficient resources.

      Resources in zones are dynamically allocated. After you confirm the purchase order, the zone you selected may fail to provide sufficient resources. As a result, the instance creation fails. We recommend that you select another zone and try again. You can visit the order list to check that the fees are refunded to you.

  • How do I authorize a RAM user to manage an RDS instance?

    For more information, see Use RAM to manage ApsaraDB for RDS permissions.

Related operations

Operation Description
CreateDBInstance Creates an ApsaraDB for RDS Instance.