tencent cloud

All product documents
TDSQL-C for MySQL
DocumentationTDSQL-C for MySQLProduct IntroductionProduct Feature List
Product Feature List
Download PDF
Last updated: 2024-12-17 17:06:41
Product Feature List
Last updated: 2024-12-17 17:06:41
Download PDF
This document compares the features supported by different instance modes of TDSQL-C for MySQL, helping you better understand the cluster characteristics of each instance mode and select products according to your needs.
Note:
In the table below, ✅ indicates supported, and - indicates unsupported or not applicable.

Supported Features

Feature Attribute
Feature Name
Provisioned Resource Instance Mode
Serverless Instance Mode
Single-Node Edition Serverless Architecture
Cluster Edition Serverless Architecture
Lifecycle
Instance Type
General type and dedicated type
-
-
Supported Version
MySQL 5.7 and MySQL 8.0
MySQL 5.7 and MySQL 8.0
MySQL 5.7 and MySQL 8.0
Number of Instances (Nodes)
1 read-write instance and 0-15 read-only instances
1 read-write instance
1 read-write instance and 1-8 read-only instances
Memory/Disk
Maximum: 88 cores and 710 GB
Compute unit configuration (CCU)
Minimum: 0.25
Maximum: 64
Compute unit configuration (CCU) Minimum: 0.25 Maximum: 64
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
-
✅
✅
-
-
✅
-
-
Monthly subscription: ✅ Pay-as-you-go: ✅
1. Compute: number of CCUs; storage: usage in GB
2. Resource pack
1. Compute: number of CCUs; storage: usage in GB
2. Resource pack
Monthly subscription: ✅
Pay-as-you-go: -
-
-
Cluster Management
✅
✅
✅
✅
✅
✅
✅
✅
✅
Instance Management
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Read-write instance: -
Read-only instance: It cannot be directly deleted, but can be reduced by modifying the configuration of the read-only instance
✅
✅
Read-write instance: ✅
Read-only instance: It cannot be directly restored, but can be added by modifying the configuration of the read-only instance
Network
✅
✅
✅
✅
✅
✅
✅
✅
✅
Configuration Adjustment
✅
Adjust the compute unit configuration: ✅
Adjust the compute unit configuration: ✅
✅
Adjust the upper limit of storage space by adjusting the compute unit configuration: ✅
Adjust the upper limit of storage space by adjusting the compute unit configuration: ✅
✅
✅
✅
-
✅
-
-
-
✅
Supported Engines
InnoDB
✅
✅
✅
Account Management
✅
✅
✅
MySQL 5.7 2.1.7 and later: ✅ MySQL 8.0 3.1.7 and later: ✅
MySQL 5.7 2.1.7 and later: ✅ MySQL 8.0 3.1.7 and later: ✅
MySQL 5.7 2.1.7 and later: ✅ MySQL 8.0 3.1.7 and later: ✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Database Management
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Parameter Management
✅
✅
✅
✅
✅
✅
✅
✅
✅
Disaster Recovery Deployment
✅
✅
✅
Backup and Rollback
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Operation Logs
✅
✅
✅
✅
✅
✅
Data Migration
Migrate from TencentDB for MySQL to the provisioned resource cluster of TDSQL-C for MySQL: ✅
-
-
✅
✅
✅
✅
✅
✅
Data Security
✅
✅
✅
✅
✅
✅
✅
✅
✅
Setting SSL Encryption
✅
✅
✅
Monitoring and Alarms
✅
✅
✅
✅
✅
✅
HTAP
MySQL 8.0 3.1.8 and later: ✅
MySQL 8.0 3.1.8 and later: ✅
MySQL 8.0 3.1.8 and later: ✅
MySQL 8.0 3.1.14 and later: ✅
MySQL 8.0 3.1.14 and later: ✅
MySQL 8.0 3.1.14 and later: ✅
✅
-
-
Database Proxy
MySQL 5.7 2.0.19 and later: ✅
MySQL 5.7 2.1.6 and later: ✅
MySQL 8.0 3.1.5 and later: ✅
MySQL 5.7 2.0.19 and later: ✅
MySQL 5.7 2.1.6 and later: ✅ MySQL 8.0 3.1.5 and later: ✅
MySQL 5.7 2.0.19 and later: ✅
MySQL 5.7 2.1.6 and later: ✅ MySQL 8.0 3.1.5 and later: ✅
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 available.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon