tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary
DocumentationTencentDB for MySQLOperation GuideInstance UpgradeUpgrading the database version of MySQL 5.5 and MySQL 5.6

Upgrading the database version of MySQL 5.5 and MySQL 5.6

PDF
Focus Mode
Font Size
Last updated: 2025-12-16 15:13:39

Overview

This document introduces how to upgrade the TencentDB for MySQL version in the console as required.
The following TencentDB for MySQL version upgrades are supported:
From MySQL 5.5 to MySQL 5.6
From MySQL 5.6 to MySQL 5.7
This document introduces the upgrades of instance database versions from MySQL 5.5 to MySQL 5.6 and from MySQL 5.6 to MySQL 5.7 in the console.
Note:
The database version cannot be downgraded.
The upgrade across major versions is not supported. For example, a MySQL 5.5 instance cannot be directly upgraded to MySQL 5.7. You must first upgrade the instance to MySQL 5.6.
Single-node Cluster Edition instances do not support database version upgrades.

Upgrade Rules

The create table ... as select ... syntax is not supported.
Source-replica sync in TencentDB for MySQL 5.6 and 5.7 is implemented based on GTID. Only InnoDB is supported by default.
MyISAM tables will be converted to InnoDB tables during upgrade from MySQL 5.5 to 5.6 if the last full backup is logical cold backup. We recommend you complete the conversion first before upgrading.
During upgrade, TencentDB for MySQL will clear the slow_log table. Save the logs before upgrading if necessary.
If an instance to be upgraded is associated with other instances (e.g., source or read-only instances), these instances will be upgraded together to ensure the data consistency.
TencentDB for MySQL upgrade involves data migration and generally takes a relatively long time. Your business will not be affected during the upgrade and can be accessed as per usual.
Instance switch will be required after version upgrade is completed (that is, the MySQL database may be disconnected for seconds). We recommend you use applications configured with auto reconnection feature and conduct the switch during the instance maintenance time. For more information, see Setting Instance Maintenance Window.
If the number of tables in a single instance exceeds one million, upgrade may fail and database monitoring may be affected. Make sure that the number of tables in a single instance is below one million.

Directions

1. Log in to the TencentDB for MySQL console, find the target instance in the instance list, and select More > Upgrade Database Version in the Operation column.
Note:
MySQL 8.0 cannot be upgraded to a later version.
2. In the displayed dialog box, select Switch Time, and click Upgrade.
3. As database upgrade involves data migration, a momentary disconnection from the MySQL database may occur after the instance upgrade is completed. You can set the switch time to During maintenance time, so that the switch will be initiated within the next maintenance time after the upgrade.
Note:
When you select During maintenance time for Switch Time, the switch will not occur immediately after the database specification upgrade is completed; instead, the sync will continue till the instance goes into the next maintenance time when the switch will be performed. As a result, the overall time it takes to upgrade the instance may be extended.


FAQs

Will TencentDB for MySQL automatically back up data before upgrade?

TencentDB for MySQL adopts the daily real-time dual-server hot backup mechanism, which supports lossless restoration of data from the last 7–1830 days based on data backup and log backup (binlog).

Can TencentDB for MySQL be downgraded from MySQL 5.7 to MySQL 5.6?

No. Database engine downgrading is not supported. To use a MySQL 5.6 instance, you need to terminate or return the existing MySQL 5.7 instance, and then purchase a MySQL 5.6 instance.

Will there be a source-replica delay during upgrade?

Source instance upgrade requires data comparison and may cause a source-replica delay.

Will the instance switch after database engine version upgrade affect my TencentDB for MySQL instance?

The upgrade won't affect your business, but the TencentDB for MySQL instance may be disconnected for a few seconds. We recommend you configure an automatic reconnection feature for your application and conduct the switch during the instance maintenance time.

How long will it take to upgrade the database engine version of a TencentDB for MySQL instance? How do I check the upgrade progress?

The time it takes depends on the instance's data volume and the read requests to replicate data. TencentDB for MySQL upgrade involves data migration and generally takes a relatively long time. Your business will not be affected during the upgrade and can be accessed as per usual.

Why is the instance always in the "Waiting for switch (after upgrade)" status?

It may be because you select During maintenance time for Switch Time, and the switch will be initiated within the next maintenance time after the upgrade. To switch immediately, find the target instance in the instance list and click Switch Now in the Operation column. The switch will cause a momentary disconnection. Make sure that your business has a reconnection mechanism.

Help and Support

Was this page helpful?

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

Feedback