tencent cloud

TDSQL-C for MySQL

DocumentaçãoTDSQL-C for MySQL

Product Feature List

Download
Modo Foco
Tamanho da Fonte
Última atualização: 2026-07-03 12:13:41
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(Total number of read-only instances = Number of read-only instances in the provisioned resource + Number of Serverless read-only instances + LibraDB read-only analysis engine)
1 read-write instance
1 read-write instance and 1-15 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
Secondary Storage
-
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
-
✅
✅
-
-
✅
-
-
Monthly subscription: ✅
Pay-as-you-go: ✅
Serverless：✅
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
✅
✅
✅
✅
✅
✅
Error Log
✅
✅
✅
Data Migration
Migrate from TencentDB for MySQL to the provisioned resource cluster of TDSQL-C for MySQL: ✅
-
-
✅
✅
✅
✅
✅
✅
Traffic Replay
✅
✅
✅
Data Security
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Monitoring and Alarms
✅
✅
✅
✅
✅
✅
HTAP
MySQL 8.0 3.1.8 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: ✅
Elasticity Management
-
✅
✅
✅
-
-
AI-Related
MySQL 8.0 3.1.19.001 and later: ✅
MySQL 8.0 3.1.19.001 and later: ✅
MySQL 8.0 3.1.19.001 and later: ✅
Próximo: Service Level Agreement

Ajuda e Suporte

Esta página foi útil?

comentários