| | |
| | Select Microsoft SQL Server. |
| | (Optional) Set an instance name. The naming rules are as follows: - Can not start with digits or hyphen (-).
- Must be 1 to 128 characters in length.
- Can only contain Chinese characters, letters, digits, underscores (_) and hyphens(-).
tip If you do not enter an instance name, it will be the same as the instance ID. |
| | You can select SQL Server 2019 Standard Edition, SQL Server 2019 Enterprise Edition, SQL Server 2019 Web Edition, SQL Server 2022 Standard Edition, SQL Server 2022 Enterprise Edition, SQL Server 2022 Web Edition. tip To create instances of SQL Server 2025 Standard Edition and SQL Server 2025 Enterprise Edition, submit a ticket to the SQL Server technical team to be added to the allowlist. This feature is currently available on an allowlist. |
Specification configuration | | Select an instance type as needed. The supported types are as follows: High availability, Single node edition, and Cluster edition. - High Availability: A classic high-availability architecture with one primary and one secondary node, suitable for production databases in large and medium-sized enterprises for scenarios like the internet, IoT, retail e-commerce, logistics, and gaming. You can select High availability as the Instance type when the Compatible version is SQL Server 2019 Standard Edition, SQL Server 2022 Standard Edition .
- Single node edition: It adopts a single node deployment architecture. Compared to typical primary and secondary instances, it comprises only one node while offering high cost-performance ratio. It is suitable for personal learning, micro-websites, and development and testing environments for small and medium-sized enterprises. You can select Single node edition as the Instance type when the Compatible version is SQL Server 2019 Standard Edition, SQL Server 2019 Enterprise Edition, SQL Server 2019 Web Edition, SQL Server 2022 Standard Edition, SQL Server 2022 Enterprise Edition, SQL Server 2022 Web Edition .
- Cluster: Features a high-availability architecture with one primary, one standby, and multiple read-only nodes. This edition is suitable for production databases in large and medium-sized enterprises, such as those in the internet, hospitality, and online education industries. You can select Cluster edition as the Instance type when the Compatible version is SQL Server 2019 Enterprise Edition, SQL Server 2022 Enterprise Edition .
|
| | Optional: Select the Include previous generations radio button to choose a specification type that includes previous generations in the Specification type section. |
| | The specification type is Exclusive Type by default. If you click the Include previous generation specifications radio button above: - When the Compatible version is later than SQL Server 2022, the Specification type only supports Exclusive Type.
- When the Compatible version is SQL Server 2022 or earlier, the Specification type supports Exclusive Type, General Type, Exclusive Type II, and General Type II. The details are as follows:
- If the Compatiable version isSQL Server 2019 Standard Edition or SQL Server 2022 Standard Edition:
- When the Instance type is High availability or Single node edition, the Specification type supports Exclusive Type, General Type, Exclusive Type II, and General Type II.
- If the Compatible version is SQL Server 2019 Enterprise Edition or SQL Server 2022 Enterprise Edition:
- When the Instance type is Cluster Edition, the Specification type supports Exclusive Type and Exclusive Type II.
- When Instance type is set to Single node edition, General type and General Type II are available for Specification type.
- If the Compatible version is SQL Server 2019 Web Edition or SQL Server 2022 Web Edition:
- When Instance type is set to Single node edition, General type and General Type II are available for Specification typeGeneral type and General Type II are available for Specification type.
|
| | Configure the node specifications and availability zones for the instance's primary and secondary nodes as needed. The details are as follows: - Node specification: Click the dropdown list to set the node specifications for the primary and secondary nodes. The secondary node's specification is the same as the primary node's by default.
tip - By default, the node specifications for SQL Server Standard Edition, Enterprise Edition, and Web Edition are all 4il-generation specifications.
- If you select Includes historical generation specifications, you can select node specifications from historical generation specifications (the 1ie and 3il specification families).
- Availability zones: Select the availability zone for the node from the drop-down list. The availability zone is the geographic location of the node. If an instance has primary and secondary nodes, you can deploy them across different availability zones.
tip - Select an availability zone close to your target users to improve access speed.
- The availability zone can not be modified after the instance is created successfully.
|
| | Only Extremely-Fast SSD PL1 Cloud Disk is currently supported. |
| | Storage space includes data file space and temporary file space. Enter a storage space between 20 GiB and 4000 GiB in 10 GiB increments. Select a value based on your business needs. |
| | Select the VPC for the instance from the dropdown list. You can also click Create VPC on the right to create a VPC. For more information, see Create a VPC. tip VPC stands for Virtual Private Cloud. A VPC is an isolated network environment that offers higher security and better performance than a traditional classic network. |
| | The subnets vary depending on the availability zones selected for the primary and secondary nodes, as follows: - If the primary and secondary nodes are in the same availability zone, the field is displayed as Subnet. Select an available subnet in the VPC from the drop-down list.
- If the primary and secondary nodes are in different availability zones, the fields are displayed as Primary node subnet and Secondary node subnet. From their respective drop-down lists, select an available subnet in the VPC for the primary and secondary nodes.
tip A subnet is a block of IP addresses within a VPC. All cloud resources in the VPC must be deployed in a subnet. The subnet assigns private IP addresses to cloud resources. For more information, see Create a subnet. |
| | Associate an allowlist with the instance. Click the allowlist text box to go to the Associate allowlist page. On this page, select an allowlist and click Confirm. You will return to the Create instance page, and the selected allowlist will appear in the allowlist text box. tip - You can also create a new allowlist on the Associate allowlist page. For more information about creating an allowlist, see Create an allowlist.
- An instance can bind a maximum of 100 allowlists.
- Click × next to the allowlist to remove it.
- If a default allowlist is set for the current account, it will appear in the allowlist box.
|
| | The system selects veyun_user by default and this cannot be modified. |
| | Set the password for the super account. The requirements are as follows: - It must contain at least three of the following character types: uppercase letters, lowercase letters, numbers, and special characters.
- Special characters include ~!@#$%^*-_+?.
- It must be 8 to 32 characters long.
- It cannot contain the string veyun_user (case-insensitive).
|
| | Enter the password again. |
| | The only supported time zone is (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. |
| | Select the character set for the instance database. Supported options include Chinese_PRC_90_CI_AI, Chinese_PRC_BIN, Chinese_PRC_BIN2, Chinese_PRC_CI_AI, Chinese_PRC_CI_AS, Chinese_PRC_CS_AS, Chinese_Taiwan_Stroke_CI_AS, Chinese_Taiwan_Stroke_CS_AS, Cyrillic_General_CI_AS, Japanese_CI_AS, Japanese_CS_AS, Latin1_General_100_CI_AS_SC_UTF8, Latin1_General_CI_AS, Latin1_General_CS_AS, SQL_Latin1_General_CP1_CI_AS, SQL_Latin1_General_CP1_CS_AS, and Thai_CI_AS. The default is Chinese_PRC_CI_AS. tip - The instance character set can not be modified after the instance is successfully created.
- Even if you select a case-sensitive instance character set, creating case-sensitive databases is not supported. For example, databases named A and a will be treated as the same database.
- For more information about the instance character set, see References.
|
| | Confirm the maintenance window for the instance. To modify, click Modify. In the Modify maintenance period dialog box, set the Maintenance window and click OK. tip - The system performs periodic maintenance on instances to ensure the stability of cloud databases. Set the maintenance window during off-peak hours to avoid affecting your business.
- During the maintenance window, your instance may experience 1 to 2 transient disconnections. Ensure your application has an automatic reconnection mechanism.
- The maintenance window duration ranges from 1 to 24 hours. The selected time range can not span across two days.
- You can modify the maintenance window of an instance after it has been created. For more information, see Set maintenance window.
|
| | Select a project for this instance from the dropdown list. The default project is default. You can also click Create new project to create a new project. For detailed instructions, see Create a new project. tip A project is a virtual concept that includes a set of resources, users, and roles. Projects allow you to centrally view and manage a group of resources and control the permissions of users and roles on these resources within the project. For more information, see Resource Management. |
| | (Optional) Add tags to the instance. tip Tags help identify and categorize cloud resources. RDS for SQL Server lets you add tags to instances for classification, simplifying instance searches and resource aggregation. For more information, see Tag overview. |
| | You can select either pay-as-you-go or subscription. If you select subscription, you need to set the subscription duration. You can also select auto-renewal, and the system will automatically renew the instance before it expires. tip You can also create a pay-as-you-go instance and switch to a subscription after confirming it meets your requirements. For more billing information, see Billing overview. |
| | Select the number of instances to create in the lower-left corner of the page. You can create up to 10 instances in a batch. tip By default, each Volcano Engine primary account can purchase up to 30 instances in each region. If you need to increase your quota to purchase more instances, go to the Quota Center to submit a Quota application. |
RDS for SQL Server
Copy page
Download PDF