Release Notes and Announcements

Release Notes

Product Announcements

Beginner's Guide

Product Introduction

Overview

Strengths

Use Cases

Architecture

Product Specifications

Instance Types

Product Feature List

Database Versions

Regions and AZs

Common Concepts

Use Limits

Suggestions on Usage Specifications

Kernel Features

Kernel Overview

Kernel Version Release Notes

Optimized Kernel Version

Functionality Features

Performance Features

Security Features

Stability Feature

Analysis Engine Features

Inspection and Repair of Kernel Issues

Purchase Guide

Billing Overview

Product Pricing

Creating Cluster

Specification Adjustment Description

Renewal

Payment Overdue

Refund

Change from Pay-as-You-Go to Yearly/Monthly Subscription

Change from Pay-as-You-Go to Serverless Billing

Value-Added Services Billing Overview

Viewing Billing Statements

Getting Started

Database Audit

Overview

Viewing Audit Instance List

Enabling Audit Service

Viewing Audit Logs

Log Shipping

Post-Event Alarm Configuration

Modifying Audit Rule

Modifying Audit Service

Disabling Audit Service

Audit Rule Template

Viewing Audit Task

Authorizing Sub-User to Use Database Audit

Serverless Service

Serverless Introduction

Creating and Managing a Serverless Cluster

Elastic Scaling Management Tool

Serverless Resource Pack

Multi-AZ Deployment

Configuration Change

FAQs

Serverless Cost Estimator

Operation Guide

Operation Overview

Switching Cluster Page View in Console

Database Connection

Instance Management

Configuration Adjustment

Instance Mode Management

Cluster Management

Scaling Instance

Database Proxy

Account Management

Database Management

Database Management Tool

Parameter Configuration

Multi-AZ Deployment

Backup and Restoration

Operation Log

Data Migration

Parallel Query

Columnar Storage Index (CSI)

Analysis Engine

Database Security and Encryption

Monitoring and Alarms

Basic SQL Operations

Connecting to TDSQL-C for MySQL Through SCF

Tag

Practical Tutorial

Classified Protection Practice for Database Audit of TDSQL-C for MySQL

Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS

Usage Instructions for TDSQL-C MySQL

New Version of Console

Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses

Strengths of Database Proxy

Selecting Billing Mode for Storage Space

Creating Remote Disaster Recovery by DTS

Creating VPC for Cluster

Data Rollback

Solution to High CPU Utilization

How to Authorize Sub-Users to View Monitoring Data

White Paper

Security White Paper

Performance White Paper

Troubleshooting

Connection Issues

Performance Issues

API Documentation

History

Introduction

API Category

Making API Requests

Instance APIs

Multi-Availability Zone APIs

Other APIs

Audit APIs

Database Proxy APIs

Backup and Recovery APIs

Parameter Management APIs

Billing APIs

serverless APIs

Resource Package APIs

Account APIs

Performance Analysis APIs

Data Types

Error Codes

FAQs

Basic Concepts

Purchase and Billing

Compatibility and Format

Connection and Network

Features

Console Operations

Database and Table

Performance and Log

Database Audit

Between TDSQL-C for MySQL and TencentDB for MySQL

Service Agreement

Service Level Agreement

TDSQL-C Policy

Data Privacy and Security Agreement

General References

Standards and Certifications

Glossary

FAQs

PDF

Focus Mode

Font Size

Last updated: 2026-01-19 17:35:27

This article describes the frequently asked questions (FAQs) related to the one-click migration feature.
1. After one-click migration, are the advanced parameters supported by the source TencentDB for MySQL instance also supported in the destination TDSQL-C for MySQL instance?
Not all parameters are supported. TDSQL-C for MySQL will gradually support these parameters. See the table below to check whether TDSQL-C for MySQL supports the advanced parameters of TencentDB for MySQL after migration.
TencentDB for MySQL 5.7
TencentDB for MySQL 8.0
TencentDB for MySQL Parameter Name
TencentDB for MySQL Parameter Value
Supported in TDSQL-C for MySQL
cdb_recycle_bin_enabled
OFF
No
information_schema_stats_expiry
86400
No
binlog_row_event_max_size
8192
No
innodb_backquery_history_limit
8000000
No
innodb_ddl_threads
4
No
innodb_parallel_ddl
OFF
No
innodb_adaptive_hash_index
OFF
Yes
cdb_plan_cache
OFF
No
innodb_table_drop_mode
sync_drop
No
cdb_recycle_bin_retention
604800
No
slave_net_timeout
120
No
innodb_backquery_enable
OFF
No
innodb_fast_ddl
OFF
No
max_length_for_sort_data
1024
Yes
slave_parallel_type
LOGICAL_CLOCK
No
cdb_optimize_large_trans_binlog
OFF
No
innodb_fast_ahi_cleanup_for_drop_table
OFF
No
txsql_parallel_exchange_buffer_size
1048576
No
innodb_temp_data_file_path
ibtmp1:12M:autoextend
No
slave_rows_search_algorithms
TABLE_SCAN,INDEX_SCAN,HASH_SCAN
No
cdb_recycle_scheduler_interval
0
No
innodb_ddl_buffer_size
10485760
No
cdb_kill_idle_trans_timeout
0
Yes
collation_server
utf8_tolower_ci
Yes
delay_key_write
ON
No
innodb_async_truncate_size
128
No
cdb_more_gtid_feature_supported
OFF
Yes
cdb_opt_outline_enabled
OFF
No
innodb_txsql_parallel_partitions_per_worker
13
No
cdb_kill_user_extra
root@%
Yes
slave_parallel_workers
0
No
innodb_backquery_window
900
No
TencentDB for MySQL Parameter Name
TencentDB for MySQL Parameter Value
Supported in TDSQL-C for MySQL
cdb_recycle_bin_enabled
OFF
No
information_schema_stats_expiry
86400
No
binlog_row_event_max_size
8192
No
innodb_backquery_history_limit
8000000
Yes
innodb_ddl_threads
4
No
innodb_parallel_ddl
OFF
No
innodb_adaptive_hash_index
OFF
Yes
cdb_plan_cache
OFF
No
innodb_table_drop_mode
sync_drop
No
cdb_recycle_bin_retention
604800
No
slave_net_timeout
120
No
innodb_backquery_enable
OFF
Yes
innodb_fast_ddl
OFF
No
max_length_for_sort_data
1024
No
slave_parallel_type
LOGICAL_CLOCK
No
cdb_optimize_large_trans_binlog
OFF
No
innodb_fast_ahi_cleanup_for_drop_table
OFF
Yes
txsql_parallel_exchange_buffer_size
1048576
No
innodb_temp_data_file_path
ibtmp1:12M:autoextend
No
slave_rows_search_algorithms
TABLE_SCAN,INDEX_SCAN,HASH_SCAN
No
cdb_recycle_scheduler_interval
0
No
innodb_ddl_buffer_size
10485760
No
cdb_kill_idle_trans_timeout
0
Yes
collation_server
utf8_tolower_ci
Yes
delay_key_write
ON
No
innodb_async_truncate_size
128
No
cdb_more_gtid_feature_supported
OFF
No
cdb_opt_outline_enabled
OFF
No
innodb_txsql_parallel_partitions_per_worker
13
No
cdb_kill_user_extra
root@%
Yes
slave_parallel_workers
0
Yes
innodb_backquery_window
900
Yes
2. After one-click migration, are the IOPS monitoring metrics from the source TencentDB for MySQL instance supported in the destination TDSQL-C for MySQL instance?
The metrics are not supported. TDSQL-C for MySQL will gradually support these metrics.
3. If the availability zone of the source TencentDB for MySQL instance is not supported by TDSQL-C for MySQL, how do I proceed with one-click migration?
If the source TencentDB for MySQL instance has only a primary instance, or its primary instance and read-only instance are in the same availability zone, you can proceed with the following steps. Go to the TDSQL-C for MySQL purchase page and check which availability zones are available in the region of the source instance, such as Guangzhou Zone 4 and Guangzhou Zone 6. In the TencentDB for MySQL console, migrate the destination instance to Guangzhou Zone 4 or Guangzhou Zone 6. Then, try the one-click migration process again.

Help and Support

Was this page helpful?

You can also Contact sales or Submit a Ticket for help.

Help us improve! Rate your documentation experience in 5 mins.

Feedback

TencentDB for MySQL Parameter Name	TencentDB for MySQL Parameter Value	Supported in TDSQL-C for MySQL
cdb_recycle_bin_enabled	OFF	No
information_schema_stats_expiry	86400	No
binlog_row_event_max_size	8192	No
innodb_backquery_history_limit	8000000	No
innodb_ddl_threads	4	No
innodb_parallel_ddl	OFF	No
innodb_adaptive_hash_index	OFF	Yes
cdb_plan_cache	OFF	No
innodb_table_drop_mode	sync_drop	No
cdb_recycle_bin_retention	604800	No
slave_net_timeout	120	No
innodb_backquery_enable	OFF	No
innodb_fast_ddl	OFF	No
max_length_for_sort_data	1024	Yes
slave_parallel_type	LOGICAL_CLOCK	No
cdb_optimize_large_trans_binlog	OFF	No
innodb_fast_ahi_cleanup_for_drop_table	OFF	No
txsql_parallel_exchange_buffer_size	1048576	No
innodb_temp_data_file_path	ibtmp1:12M:autoextend	No
slave_rows_search_algorithms	TABLE_SCAN,INDEX_SCAN,HASH_SCAN	No
cdb_recycle_scheduler_interval	0	No
innodb_ddl_buffer_size	10485760	No
cdb_kill_idle_trans_timeout	0	Yes
collation_server	utf8_tolower_ci	Yes
delay_key_write	ON	No
innodb_async_truncate_size	128	No
cdb_more_gtid_feature_supported	OFF	Yes
cdb_opt_outline_enabled	OFF	No
innodb_txsql_parallel_partitions_per_worker	13	No
cdb_kill_user_extra	root@%	Yes
slave_parallel_workers	0	No
innodb_backquery_window	900	No

tencent cloud

TDSQL-C for MySQL

FAQs

1. After one-click migration, are the advanced parameters supported by the source TencentDB for MySQL instance also supported in the destination TDSQL-C for MySQL instance?

2. After one-click migration, are the IOPS monitoring metrics from the source TencentDB for MySQL instance supported in the destination TDSQL-C for MySQL instance?

3. If the availability zone of the source TencentDB for MySQL instance is not supported by TDSQL-C for MySQL, how do I proceed with one-click migration?

Help and Support