This document describes how to create a TencentDB for MySQL instance in the console.
Prerequisites
You have registered a Tencent Cloud account and completed identity verification.
To register a Tencent Cloud account:
To complete identity verification:
Note:
The new purchase page allows you to import existing configuration. If the logged-in account has an existing TencentDB for MySQL instance, this feature can automatically configure the new instance parameters on the purchase page, making it easier for you to adjust the existing configuration or directly purchase a new instance as follows:
1. On the purchase page, click Import Existing Configuration in the top-right corner.
2. In the pop-up window, select the existing target instance in the corresponding region and click OK.
Purchasing in the console
1. Log in to the TencentDB for MySQL purchase page, complete Basic Configuration and Instance Configuration as needed, and click Next: Set Network and Database.
Basic Configuration
Billing Mode: Monthly subscription and pay-as-you-go billing are supported.
If your business has a stable long-term demand, we recommend that you select monthly subscription.
If the request volume of your business fluctuates greatly and instantaneously, we recommend that you choose pay-as-you-go billing.
Region: Select the region where you want to deploy your TencentDB for MySQL instance. We recommend that you use the same region as the CVM instance to be connected to. Tencent Cloud services in different regions cannot communicate with each other over the private network. The region cannot be modified after purchase.
Database Version: Currently, TencentDB for MySQL supports MySQL 8.0, 5.7 and 5.6. For more information on the features of each version, see MySQL 5.7 Reference Manual.
Note：
It is recommended to use the more recent database versions of MySQL 8.0 and 5.7.
The cluster edition architecture only supports the selection of MySQL versions 8.0 and 5.7.
Engine: Select InnoDB or RocksDB.
InnoDB: The most commonly used OLTP storage engine, with complete transaction support and powerful capability of highly concurrent reads/writes.
RocksDB: A key-value storage engine, with efficient writing and high compression. If it is selected, the architecture will be two-node.
Architecture: Single-node, two-node, three-node and cluster edition architectures are supported. For more information, see Database Architecture Overview.
Disk Type: The hard disk is used to store the files required by MySQL execution. TencentDB for MySQL supports local disk and cloud disk.
Two-node and three-node instances use local SSD disks.
Single-node instances use cloud disks.
Availability Zone: Two-node, three-node, and cluster edition architectures allow for the selection of a source availability zone and a replica availability zone. Selection of different source and replica zones (i.e.multi-AZ deployment), enhances database protection against failures or disruptions within an availability zone.
For two-node and three-node architectures, it is necessary to select a source availability zone and a replica availability zone.
For cluster edition architecture, you must choose the number of read-only nodes, as well as the availability zones for both read-write and read-only nodes.
Number of Read-Only Nodes: By default, there are two read-only nodes, supporting manual selection of one to five nodes.
Read-Write Node Availability Zone: Select the availability zone for the read-write nodes.
Read-Only Node Availability Zone: Depending on the number of read-only nodes, sequentially select the availability zones for these nodes. The specific range of availability zones is subject to the actual purchase page. If the availability zones for the read-only nodes are not actively selected, the system will automatically allocate them.
Note:
If the source and replica are in different AZs, the network sync delay may increase by 2–3 ms.
When you purchase Tencent Cloud services, we recommend that you select the region closest to your end users to minimize access latency and improve download speed.
Instance Configuration
Filter: You can quickly filter the needed CPU and memory specifications for the instance. By default, all CPU and memory specifications are selected.
Type: By default, single-node is of the Basic instance type. Two-node and three-node provide General and Dedicated instance types. Cluster edition provides Standard and Enhanced instance types. For more details, see Isolation Policy.
Instance Specs: Select specifications as needed.
Hard Disk: Select the disk size. The disk is used to store the files required by MySQL execution.
For hard disks with single-node and cluster edition architectures, the disk type is cloud disk. After the disk capacity is selected and the instances are created, users can only expand the disk capacity; scale-in is not currently supported. For information on disk types, see Disk Types.
Single-node supports SSD and Enhanced SSD Cloud Disks. The selectable disk capacities range from 20 to 30,000 GB.
The cluster edition supports Tremendoust SSD, Enhanced SSD, and SSD Cloud Disks. The selectable disk capacities range from 20 to 30,000 GB.
Data Protection Space: To ensure the recoverability of the database instances, cluster edition instances must allocate a designated amount of space specifically for data protection within the instances. This reserved space is not used for data storage and is categorized as system protection space, designed to prevent potential instance malfunctions resulting from data overflow. The setting range is 1 - 10 GB, with the default of 1GB.
2. Configure Network and Others and Database Settings and click Next: Confirm the configuration info.
Network and Others
Network: You can select the network and subnet for the instance. VPC is supported. If existing networks do not meet your requirements, you can create VPCs or subnets.
Note:
A subnet is a logical network space in a VPC. You can create subnets in different AZs in the same VPC, which communicate with each other over the private network by default.
After you select a network, the subnet IPs in the AZ of the selected instance are displayed by default. You can also select subnet IPs in other AZs in the region of the instance. Business connections adopt nearby access, so the network latency will not be increased.
We recommend that you select the same VPC in the same region as the CVM instance to be connected to. Otherwise, the MySQL instance cannot connect to the CVM instance over the private network.
Custom Port: The database access port, which is 3306 by default.
Port 3306 must be opened for the TencentDB for MySQL instance through the inbound rule of the security group. The instance uses private network port 3306 by default and supports custom port. If the default port is changed, the new port should be opened in the security group.
Project: Select a project to which the TencentDB instance belongs. The default project is used.
Tag: Categorize and manage resources with tags. For more information, see Tag Overview.
Alarm Policy: You can create an alarm policy to trigger alarms and send messages when the Tencent Cloud resource state changes. For more information, see Alarm Policies (Cloud Monitor).
Database Settings
Instance Name: Name the instance now or later.
Data Replication Mode: For selecting a replication method for Non-single-node instances, see Database Instance Replication.
By default, two-node instances are configured for asynchronous replication. Two methods of replication (asynchronous and semi-synchronous) are provided for two-node instances.
By default, three-node instances are configured for asynchronous replication. Three methods of replication (asynchronous, semi-synchronous, and fully synchronous) are provided for three-node instances.
By default, cluster edition instances are configured for semi-synchronous replication. Two methods of replication (asynchronous and semi-synchronous) are provided for cluster edition instances.
Parameter Template: Besides the system parameter template provided by TencentDB, you can create a custom parameter template. For more information, see Managing Parameter Template.
Character Set: LATIN1, GBK, UTF8, and UTF8MB4 character sets are supported. The default value is UTF8. After purchasing the instance, you can change the character set on the instance details page in the console. For more information, see Use Limits > Notes on character set.
Collation: The instance character set provides a case- and accent- sensitive collation for system data.
Table Name Case Sensitivity: Specify whether the table name is case-sensitive. Note that this configuration cannot be modified once set for MySQL 8.0.
Password Complexity: Only two-node, three-node, cluster edition instances support setting of password complexity to enhance database security. It is disabled by default. For more information, see Setting Password Complexity.
Root Password: Set the password of the root account (the default user name for a new MySQL database is "root"). If you select Set After Creation, you can reset the password after creating the instance. For more information, see Resetting Password.
3. Confirm the selected configuration items (if you need to modify them, click Edit to return to the corresponding step and make changes), read and indicate your consent to the Terms of Service, confirm the Validity Period and Quantity, and click Buy Now.
4. You will be returned to the instance list after you purchase the instance. The instance will be in the Delivering status. You can use the instance after around 3–5 minutes when its status changes to Running.
Subsequent operations
You can access the TencentDB for MySQL instance over both private and public networks from a Windows or Linux CVM instance. For more information, see Connecting to MySQL Instance.
Yes
No
Was this page helpful?