Creating an Instance
Last updated:2026-02-10 11:06:00
This document describes how to create a TDSQL Boundless instance via the console.
Prerequisites
A Tencent Cloud account has been registered with identity verification completed.
To register a Tencent Cloud account: click Sign up for a Tencent Cloud account.
To complete identity verification: click here to complete identity verification.
Operation Steps
1. Log in to TDSQL Boundless console, in the instance list, click Create to go to the purchase page.
2. On the purchase page, select relevant configurations.
Basic Configuration
Engine: Select TDSQL Boundless.
Billing Mode: Supports yearly/monthly subscription and pay-as-you-go. If business volume has stable long-term demand, it is recommended to choose yearly/monthly subscription. If business volume has scenarios with sudden significant fluctuations, it is recommended to choose pay-as-you-go.
Region: Select the region where your business needs to deploy TDSQL Boundless. We recommend choosing the same region as your CVM. Cloud products in different regions are inaccessible via private networks, and the region cannot be changed after purchase.
Network: Supports the environment of a private network. You can select the VPC and subnet to which the instance belongs. If the existing network is unsuitable, you can create a VPC or create a subnet.
Note:
Subnet is a logical network space within a VPC. You can create subnets in different AZs under the same VPC. Subnets in different AZs under the same VPC can interconnect via the private network by default.
After the network is selected, the subnet IP address defaults to that of the same AZ as the selected instance. You may also manually choose subnet IP addresses within other AZs in the same region. Business connections follow proximity-based routing logic without adding network latency.
It is recommended to choose the same VPC as your CVM in the same region; otherwise, the CVM and database will be unable to connect via the private network. The default setting is Default-VPC (default).
Specs Configuration
Instance Type: Divided into cluster edition and basic edition.
Cluster Edition: Composed of multiple nodes, it delivers high-performance and highly available database services as a unified cluster, suited for enterprise production environments.
Basic Edition: Consists of a single node, providing complete features of the database at a lower cost. It lacks high availability capabilities and is only suitable for personal users to learn and experience product features.
Warning:
The Basic Edition does not support high availability capabilities. Enterprise users should not deploy Basic Edition instances in production environments, as this risks short-term service interruptions impacting business operations.
Note:
Basic Edition instances can be upgraded to Cluster Edition via the console after creation; however, Cluster Edition instances cannot be downgraded to Basic Edition after creation.
Deployment Mode: Users can select the number of AZs for deployment. Single-AZ deployment: All resources reside in the same AZ, delivering the lowest network latency; Dual-AZ deployment: Applications run across two AZs to withstand a single AZ failure; Triple-AZ deployment: Resources are distributed across three AZs, enabling continuous service availability and shortened recovery time in the event of any single AZ failure.
AZ: For instances deployed across multiple AZs, users can designate a primary AZ. Once set, the TDSQL Boundless nodes in this AZ will have their weight increased to 99%, meaning 99% of requests will be routed to these nodes for processing. Users may choose not to set a primary AZ, or can cancel/adjust this setting via the console.
After the primary AZ is set, the configuration adjustment feature becomes unavailable unless the user temporarily unsets the primary AZ. This is because TDSQL cannot proactively switch the Leader to a different AZ during configuration changes to ensure business continuity. If this operation is required, please be aware of potential performance impacts before the primary AZ is unset to proceed with configuration changes.
Number of Fully Functional Replicas: Select the number of replicas capable of read and write operations and participating in voting for data consistency.
Note:
Setting the weight of TDSQL Boundless nodes in the primary AZ to 100% is not currently supported.
Hybrid Node Disk Type: Includes General Purpose SSD CBS, Enhanced SSD, and local SSD.
Enhanced SSD: A storage type designed by Tencent Cloud based on next-generation storage engines, leveraging NVMe SSD storage media and network infrastructure. It is suitable for I/O-intensive scenarios with demanding low-latency requirements, such as medium-to-large databases.
Local SSD: A storage type based on local NVMe SSDs, delivering ultra-high IOPS and high-throughput storage resources. It is suitable for I/O-intensive scenarios such as large-scale high-performance relational databases.
Hybrid Node Disk Capacity: Select the storage space required for each node.
Hybrid Nodes: Select the number of peer nodes needed.
Management Nodes: The system automatically configures the required number of management nodes for peer nodes to perform necessary instance management.
Management Node Specs: The system automatically configures the required management node specifications for peer nodes to perform necessary instance management.
Initialization configurations
Character Set: Supports UTF8, LATIN1, GBK, and UTF8MB4 character sets. The default character set encoding format is UTF8MB4.
Table Name Case Sensitivity: Specifies whether table names are case-sensitive. Note that in MySQL 8.0, the case sensitivity setting for table names cannot be changed after configuration. Please configure with caution.
Custom Port: The access port for the database. The default is 3306.
Tag: Add tags to the instance to facilitate categorizing and managing instance resources.
Instance Name: You can choose to name the instance after creation or immediately.
3. After confirming the above configurations, read and select the service terms, then click Buy Now. After a successful purchase, return to the Instance List. You will see the instance status as "creating" (this typically takes 3~5 minutes; please wait patiently). Once the instance status changes to "running", normal operations can be performed.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback