This topic describes how to create an ApsaraDB RDS for SQL Server instance in the ApsaraDB RDS console. You can also call an API operation to create an ApsaraDB RDS for SQL Server instance.
For more information, see Pricing, billable items, and billing methods.
You have an Alibaba Cloud account. For more information, see Sign up with Alibaba Cloud.
- Log on to the ApsaraDB RDS console.
- Configure the following parameters.
Parameter Description Billing Method
Note A maximum of 30 pay-as-you-go RDS instances are allowed per Alibaba Cloud account. To increase this quota, you must submit a ticket.
- Subscription: A subscription instance is an instance that you can subscribe to for a specified period and pay for up front. For long-term use, the subscription billing method is more cost-effective than the pay-as-you-go billing method. 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. The pay-as-you-go billing method is suitable for short-term use. If you no longer need your pay-as-you-go instance, you can release it to reduce costs.
Region The region to which the RDS instance belongs.
- After you confirm the purchase order, you cannot change the selected region.
- We recommend that you select a region that is in close proximity to the geographic location where your users reside. This allows you to increase the access speeds of your users.
- The RDS instance must reside in the same region as the ECS instance that you want to connect. If the RDS and ECS instances reside in different regions, these instances cannot communicate over an internal network. In this case, these instances must communicate over the Internet and therefore cannot deliver optimal performance.
Database Engine The database engine and version that the RDS instance runs. Select Microsoft SQL Server. The supported SQL Server versions are 2008 R2, 2012, 2016, 2017, and 2019.Note The available database engines and versions vary based on the region that you select. Edition
Note The available RDS editions vary based on the region and database engine version that you select. For more information, see Overview of ApsaraDB RDS editions.
- Basic: The database system consists of only a primary RDS instance. Computing is separated from storage to increase cost-effectiveness.
- High-availability: The database system consists of a primary RDS instance and a secondary RDS instance. These instances work in the high-availability architecture.
- Cluster: The database system consists of a primary RDS instance, a secondary RDS instance, and up to seven read-only RDS instances. The read capability of the database system improves with the number of read-only RDS instances.
- Local SSD: A local SSD resides on the same server as the database engine. You can store data on local SSDs to reduce I/O latency.
- Enhanced SSD: An enhanced SSD is an ultra-high performance disk that is developed by Alibaba Cloud
based on the next-generation distributed block storage architecture. It integrates
25 Gigabit Ethernet and remote direct memory access (RDMA) technologies. This type
of storage media reduces one-way latency and delivers up to 1 million random input/output
operations per second (IOPS). Three enhanced SSD options are provided in the ApsaraDB
RDS console. Each option represents a specific performance level (PL).
- ESSD PL1: This option represents an enhanced SSD of PL1.
- ESSD PL2: An enhanced SSD of PL2 delivers IOPS and throughput that are twice higher than those delivered by an enhanced SSD of PL1.
- ESSD PL3: An enhanced SSD of PL3 delivers IOPS that is 20 times higher than the IOPS delivered by an enhanced SSD of PL1. It also delivers throughput that is 11 times higher than the throughput delivered by an enhanced SSD of PL1. Enhanced SSDs of PL3 are suitable for workloads that require high I/O performance to process concurrent requests. Enhanced SSDs of PL3 are also suitable for workloads that require stable read/write latency.
- Standard SSD: A standard SSD is an elastic block storage device that is designed based on the distributed storage architecture. You can store data on standard SSDs to separate computing from storage.
For more information, see Storage types.Note If you select the standard SSD or enhanced SSD storage type, you can enable Disk Encryption. This allows you to maximize protection for your data. For more information, see Configure disk encryption for an ApsaraDB RDS for SQL Server instance.
Zone of Primary Node and Zone of Secondary Node A zone is an independent physical location within a region. The Zone of Primary Node parameter specifies the zone to which the primary RDS instance belongs. The Zone of Secondary Node parameter specifies the zone to which the secondary RDS instance belongs.You can select the Single-zone Deployment or Multi-zone Development method.
- Single-zone Deployment: If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are the same.
- Multi-zone Development: This is the recommended deployment method. If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are different. This allows you to provide zone-level disaster recovery. You must manually specify the Zone of Primary Node and the Zone of Secondary Node.
- After the RDS instance is created, you can view information about the RDS instance and its secondary RDS instance on the Service Availability page.
- If you select the RDS Basic Edition, the database system consists of only one primary RDS instance and supports only the single-zone deployment method.
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.
- General-purpose (Entry-level): specifies the general-purpose instance family. A general-purpose instance exclusively occupies the allocated memory and I/O resources. However, it shares CPU and storage resources with the other general-purpose instances that are deployed on the same server.
- Dedicated (Enterprise-level): specifies the dedicated instance family or the dedicated host instance family. A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. The dedicated host instance family is the highest configuration of the dedicated instance family. A dedicated host instance exclusively occupies all the CPU, memory, storage, and I/O resources of the server on which the instance is deployed.
- Dedicated: A dedicated cluster exclusively occupies all the resources on a VM or physical host. The permissions to manage hosts in a dedicated cluster can be authorized to you. This allows you to create multiple database instances on a host. For more information, see Add hosts.
Capacity The storage capacity that is provided for the RDS instance to store data files, system files, binary log files, and transaction files. You can adjust the storage capacity in increments of 5 GB.Note Dedicated instances are allocated exclusive resources. Therefore, the storage capacity of a dedicated instance that is equipped with local SSDs varies based on the instance type. For more information, see Primary ApsaraDB RDS instance types.
- Click Next: Instance Configuration.
- In the lower-right corner of the page, click Next: Instance Configuration.
- Configure the following parameters.
Parameter Description Network Type Set the network type.
Note The RDS instance must have the same network type as the ECS instance that you want to connect. If the RDS and ECS instances both have the VPC network type, these instances must also reside in the same VPC. Otherwise, these instances cannot communicate over an internal network.
- Classic Network: the traditional type of network.
- VPC: the recommended type of network. A virtual private cloud (VPC) is an isolated virtual
network that provides higher security and higher performance than the classic network.
After you select the VPC network type, you must specify the VPC and VSwitch of Primary Node parameters. If you set the Deployment Method parameter in the previous step to Multi-zone deployment, you must also specify the VSwitch of Secondary Node parameter.
- Click Next: Confirm Order.
- Confirm the settings in the Parameters section, specify the Purchase Plan parameter and the Duration parameter, read and select Terms of Service, and then click Pay Now to complete the payment. You must specify the Duration parameter only when the RDS
instance uses the subscription billing method.Note When you create a subscription RDS instance, we recommend that you select Auto-Renew Enabled. This relieves the need to manually renew the RDS instance on a regular basis. This also allows you to avoid interruptions to your workloads due to overdue payments.
On the ApsaraDB RDS homepage, click Instances in the left-side navigation pane, select the region where the RDS instance resides in the top navigation bar, and then find the RDS instance based on the Creation Time.
What to do next
- Configure an IP address whitelist for an ApsaraDB RDS for SQL Server instance
- Create an account and a database for an ApsaraDB RDS instance that runs SQL Server 2008 R2
- Create an account and a database for an ApsaraDB RDS instance that runs SQL Server 2012, 2016, 2017 SE, or 2019 SE
- Create accounts and databases for an ApsaraDB RDS instance that runs SQL Server 2017 EE or 2019 EE
- Apply for or release a public endpoint on an ApsaraDB RDS for SQL Server instance
- Connect to an ApsaraDB RDS for SQL Server instance
- After I submit the order for purchasing an RDS instance, why does the ApsaraDB RDS
console not respond and why am I unable to find the created RDS instance?
The issue may occur due to the following reasons:
- The RDS instance does not reside in the region that you selected.
In the top navigation bar, select the region where the RDS instance resides. Then, you can find the RDS instance.
- The zone that you selected cannot provide sufficient resources.
Resources in zones are dynamically allocated. After you submit the purchase order, the zone that you selected may be unable to provide sufficient resources. As a result, the RDS instance cannot be created. We recommend that you select a different zone and try again. If the RDS instance still cannot be created, you can go to the the Orders page in the Billing Management console to view the refunded fee.
- The RDS instance does not reside in the region that you selected.
- How do I authorize a RAM user to manage my RDS instance?
For more information, see Use RAM to manage ApsaraDB RDS permissions.
|Create an instance||Creates an ApsaraDB RDS instance.|