Step 1: Buy a DB Instance
This section describes how to create a DB instance on the RDS console.
The DB instance class and storage space you need depend on your processing power and memory requirements.
- You have registered a HUAWEI CLOUD account.
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Database, click RDS. The RDS console is displayed.
- On the Instance Management page, click Buy DB Instance.
- On the displayed page, select a billing mode, configure information about your DB instance. Then, click Next.
Table 1 Basic information
A region where the tenant is located. It can be changed in the upper left corner of the page.NOTE:
Products in different regions cannot communicate with each other through a private network and you cannot change the region of a DB instance after creating the instance. Therefore, exercise caution when selecting a region.
DB Instance Name
Must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
- If you intend to create multiple DB instances and read replicas, the length of each DB name will change.
- If you create multiple DB instances at a time, they will be named with four digits appended to the DB instance name. For example, if you enter instance, the first instance will be named as instance-0001, the second as instance-0002, and so on.
Set to Microsoft SQL Server.
DB Engine Version
For details, see DB Engines and Versions.
Different DB engine versions are supported in different regions.
If you use a Microsoft SQL Server database, select a proper DB engine version based on service requirements. You are advised to select the latest available version because it is more stable, reliable, and secure.
DB Instance Type and AZ
- Primary/Standby: uses the HA architecture with a primary DB instance and a synchronous standby DB instance. It is suitable for production databases of large- and medium-sized enterprises in Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other sectors. The standby DB instance improves instance reliability and is invisible to you after being created.
An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. Some regions support both single AZs and multiple AZs and some only support single AZs.
To achieve higher reliability, RDS will automatically deploy your primary and standby instances in different physical servers even if you deploy primary and standby DB instances in the same AZ. If you attempt to create primary/standby DB instances in the same AZ in a Dedicated Computing Cluster (DCC) and there is only one physical server available, the creation will fail.
RDS supports deploying primary and standby DB instances in an AZ or across AZs. You can determine whether the standby AZ is the same as the primary AZ.
- If they are the same (default setting), the primary and standby DB instances are deployed in the same AZ.
- If they are different, the primary and standby DB instances are deployed in different AZs to ensure failover support and high availability.
- Single: uses the single-node architecture, which is more cost-effective than mainstream primary/standby DB instances. It is suitable for developing and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.
Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.
- Ultra-high I/O: supports a maximum throughput of 350 MB/s.
If you select DSS for Resource Type, only the storage type that you have selected when buying the DSS service is displayed by default.
You need to select a time zone for your DB instance according to the longitude and latitude of the region hosting your DB instance. Can be specified only when you create a DB instance and cannot be modified after the DB instance is created.
Defines a collation of a database or table column, or a collation cast operation when applied to character string expression. It acts as the default collation for the DB instance.
Table 2 Instance specifications
Refers to the CPU and memory of a DB instance. Different instance classes refer to different numbers of database connections and maximum IOPS.
For details about instance classes, see DB Instance Classes.
RDS DB instances have the following specifications:
- Shared: The allocated memory and I/O resources are exclusive. The vCPUs and storage space are shared by DB instances on the same physical server. Storage size is not bound to vCPUs and memory and can be flexibly configured. In this way, the utilization rate is maximized and cost effectiveness is improved.
The shared specifications are suitable for users who have a small budget and have low requirements on performance stability.
- Exclusive: The vCPUs, memory, storage space, and I/O resources are exclusive. The performance is stable and is not affected by other DB instances on the same physical server. The premium configuration is that a DB instance exclusively occupies all resources of a physical server.
The exclusive specifications are suitable for database-centered scenarios such as finance, e-commerce, government, and large- and medium-scale Internet business.
After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.NOTE:
DB instances in a DCC only support the general-enhanced instance class.
This option is displayed only when you buy the DSS service.
This option is displayed only when you select DSS for Resource Type. The storage pool is physically isolated from other pools and is secure.
Storage Space (GB)
Contains the system overhead required for inode, reserved block, and database operation. Can range in size from 40 GB to 4000 GB and can be scaled up only by a multiple of 10 GB.
After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space.
- Disabled: indicates the encryption function is disabled.
- Enabled: indicates the encryption function is enabled, improving data security but affecting system performance.
Key Name: indicates the tenant key. You can create or select a key.NOTE:
- Once the disk encryption function is enabled, you cannot disable it or change the key after a DB instance is created. The backup data stored in OBS is not encrypted.
- After an RDS DB instance is created, do not disable or delete the key that is being used. Otherwise, RDS will be unavailable and data cannot be restored.
- For details about how to create a key, see the "Creating a CMK" section in the Data Encryption Workshop User Guide.
Table 3 Network
A dedicated virtual network in which your RDS DB instances are located. Isolates networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.
If no VPC is available, RDS allocates a VPC to you by default.
Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function must be enabled by default for subnets in which you plan to create RDS DB instances and cannot be disabled.
A floating IP address is automatically assigned when you create a DB instance. You can also enter an unused floating IP address in the subnet segment. After the DB instance is created, you can change the floating IP address.
Enhances security by controlling access to RDS from other services. You need to add rules to a security group that enable you to connect to your DB instance.
If no security group is available, RDS allocates a security group to you by default.NOTE:
To configure the Active Directory (AD) domain for the DB instance, ensure that the DB instance and domain controller must be in the same security group.
Table 4 Database configuration
- Configure (default value): Configure the password when you are creating the DB instance.
- Skip: The system does not set an initial password for you.
To log in, you will have to reset a password for the DB instance.
After a DB instance is created, you can reset the password. For details, see Resetting the Administrator Password.
The default login name for the database is rdsuser.
Must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_+?,). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.
Keep this password secure. The system cannot retrieve it.
After a DB instance is created, you can reset this password. For details, see Resetting the Administrator Password.
Must be the same as Administrator Password.
Contains engine configuration values that can be applied to one or more DB instances. If you intend to create primary/standby DB instances, they use the same parameter template. You can modify instance parameters as required after the DB instance is created.NOTICE:
If you use a custom parameter template when creating a DB instance, the specification-related parameter max server memory (MB) in the custom template is not delivered. Instead, the default value is used.
You can modify the instance parameters as required after the DB instance is created. For details, see section Modifying Parameters in a Parameter Template.
If the DB instance has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list.
You can also go to the ProjectMan console to create a project. For details about how to create a project, see the ProjectMan User Guide.
Table 5 AD domain
Allows an Active Directory user to authenticate with Microsoft SQL Server DB instances.
Active Directory, which is short for AD, is a directory service on Windows Standard Server, Windows Enterprise Server, and Windows Datacenter Server. Active Directory stores information about objects on the network and makes this information easy for administrators and users to find and use. Active Directory uses a structured data store as the basis for a logical, hierarchical organization of directory information.NOTICE:
- When you configure an AD domain information during the DB instance creation, do not configure or disable Group Policy Object (GPO) for your domain controller server. Otherwise, the DB instance creation will fail.
- If GPO is required, you need to buy an ECS and set up a new domain controller server with GPO disabled. Then, establish trust between your domain controller server and the new domain controller server. For details, contact customer service.
- Skip: This option is selected by default.
- Configure: To configure the AD domain, you must first prepare a domain controller on an ECS or on-premises database. Then, configure the directory address, domain name, directory administrator, and directory administrator password as required.
If a Microsoft SQL Server single DB instance is configured with the AD domain, it cannot be changed to primary/standby DB instances.
DB instances of Microsoft SQL Server 2017 Enterprise Edition, 2017 Standard Edition, and 2017 Web Edition do not support AD domain configuration.
Enter the private IP address of the ECS that supports the AD domain. After the DB instance is created, you can view the directory address in the DB Information area on the Basic Information page.
Example value: 192.168.x.x.
A fully qualified domain name, such as DBStest.com, must:
- Be the same as the ECS domain name.
- Be no more than 48 characters long.
- Only include letters, digits, dots (.), and hyphens (-).
- Include a valid top-level domain name which is more than 2 characters long and contains only dots (.) and letters, for example, .com
- After the DB instance is created, you can view the directory address in the DB Information area on the Basic Information page.
You are advised to enter the domain administrator username.
Directory Administrator Password
Indicates the password of the directory administrator.
Keep this password secure. The system cannot retrieve it.
Table 6 Tags
Tags an RDS DB instance. This configuration is optional. Adding tags to RDS DB instances helps you better identify and manage the DB instances. A maximum of 10 tags can be added for each DB instance.
After a DB instance is created, you can view its tag details on the Tags page. For detailed operations, see Managing Tags.
Table 7 Purchase period
RDS supports batch creation of DB instances. If you intend to create primary/standby DB instances and set Quantity to 1, a primary DB instance and a synchronous standby DB instance will be created.
If you have any questions about the price, click Pricing details at the bottom of the page.
The performance of your DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.
- Confirm the specifications for pay-per-use DB instances.
- If you need to modify your settings, click Previous.
- If you do not need to modify your settings, click Submit.
- To view and manage the DB instance, go to the Instance Management page.
- During the creation process, the DB instance status is Creating.
- To refresh the DB instance list, click in the upper right corner of the list. When the creation process is complete, the instance status will change to Available.
- The automated backup policy is enabled by default. An automated full backup is immediately triggered after a DB instance is created.
- After a DB instance is created, you can enter a description for it.
- The default database port number is 1433. After a DB instance is created, you can change its port number.
You are advised to change the database port in a timely manner.
For details, see Changing the Database Port.