Release Notes
Last updated: 2025-12-31 17:26:11
December 2025
Update | Description | Release Date | Documentation |
Database proxy version update | TencentDB for MySQL released database proxy version 1.4.6. | 2025-12-16 |
November 2025
Update | Description | Release Date | Documentation |
LibraDB kernel version update | TencentDB for MySQL analysis engine has released new Linux kernel versions 4.2506.2.0 and 2.2410.14.0, introducing multiple new kernel features while implementing system issue fixes and optimizations. | 2025-11-27 | |
TXSQL kernel feature update | The new kernel versions 20221002 and 20241009 were released for TencentDB for MySQL 8.0. | 2025-11-26 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.20. | 2025-11-11 | |
Free trial of audit logs and SQL analysis | A 30-day free trial was provided for the database audit feature of TencentDB for MySQL and the SQL analysis feature of TencentDB for DBbrain (DBbrain). | 2025-11-03 |
October 2025
Update | Description | Release Date | Documentation |
Support for enabling instance termination protection | The existing and newly purchased TencentDB for MySQL instances supported enabling instance termination protection. Once enabled, the instances could not be terminated directly through the console or API, effectively preventing accidental instance termination. | 2025-10-30 | |
Network forwarding mode supported by the database proxy | The database proxy of instances with the TencentDB for MySQL Cluster Edition (cloud disk) architecture supported enabling network forwarding. Once enabled, SQL distribution would be performed through network forwarding. | 2025-10-30 | |
Release of a new version of the Instance Details page | A new version of the Instance Details page of TencentDB for MySQL was released, showing the instance information, network information, specification configuration, resource usage, and instance architecture diagram more clearly to help enhance the instance operation management capabilities. | 2025-10-28 | |
LibraDB kernel version update | New kernel versions 3.2503.7.0 and 2.2410.13.0 were released for the analysis engine of TencentDB for MySQL. They supported multiple new kernel features, fixed system issues, and optimized the system. | 2025-10-24 | |
New regions supported by the analysis engine | The regions Hong Kong (China) and Nanjing were supported for the analysis engine of TencentDB for MySQL. | 2025-10-22 | |
LibraDB kernel version update | The new kernel version 4.2506.1.0 was released for the analysis engine of TencentDB for MySQL. It supported multiple new kernel features and optimized the system. | 2025-10-21 | |
TXSQL kernel feature update | The new kernel version 20250803 was released for TencentDB for MySQL 5.7. | 2025-10-16 | |
LibraDB kernel version update | The new kernel version 3.2503.6.0 was released for the analysis engine of TencentDB for MySQL. It supported multiple new kernel features, fixed system issues, and optimized the system. | 2025-10-10 | |
Automatic row-based storage and column-based storage node forwarding policy supported by the database proxy | The database proxy version 1.4.5 supported configuring request forwarding to read-only or read-write instances when the read-only analysis engine failed. It also supported forwarding SQL requests to the read-only analysis engine based on the read weight. | 2025-10-10 | |
Viewing slow SQL details supported by the analysis engine | Slow SQL details and SQL analysis reports for read-only analysis engine instances could be viewed in the console. | 2025-10-10 |
September 2025
Update | Description | Release Date | Documentation |
Flagship instances supported by Cluster Edition | TencentDB for MySQL flagship instances with the Cluster Edition architecture were launched in regions outside the Chinese mainland (Singapore, Frankfurt, and Jakarta), which provide higher performance. | 2025-09-26 | |
New regions supported by the analysis engine | The Frankfurt region was supported for the analysis engine of TencentDB for MySQL. | 2025-09-22 | |
LibraDB kernel version update | New kernel versions 3.2503.5.0 and 2.2410.12.0 were released for the analysis engine of TencentDB for MySQL. They supported multiple new kernel features, fixed system issues, and optimized the system. | 2025-09-15 | |
TXSQL kernel feature update | The new kernel version 20250802 was released for TencentDB for MySQL 5.7. | 2025-09-10 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.4.5. | 2025-09-08 |
August 2025
Update | Description | Release Date | Documentation |
LibraDB kernel version update | The new kernel version 2.2410.11.1 was released for the analysis engine of TencentDB for MySQL. It supported multiple new kernel features, fixed system issues, and optimized the system. | 2025-08-28 | |
TXSQL kernel feature update | The new kernel version 20241005 was released for TencentDB for MySQL 8.0. | 2025-08-25 | |
TXSQL kernel feature update | The new kernel version 20250730 was released for TencentDB for MySQL 5.7. | 2025-08-25 | |
Support for shipping database audit logs to COS | The database audit feature of TencentDB for MySQL supported shipping logs to Cloud Object Storage (COS). COS provided stable, durable, and low-cost storage services. Audit logs were stored in COS to meet the requirements for long-term data storage. | 2025-08-12 | |
New regions supported by the analysis engine | The regions Virginia and São Paulo were supported for the analysis engine of TencentDB for MySQL. | 2025-08-05 | |
LibraDB kernel version update | New kernel versions 3.2503.4.0 and 2.2410.10.1 were released for the analysis engine of TencentDB for MySQL. They supported multiple new kernel features, fixed system issues, and optimized the system. | 2025-08-05 |
July 2025
Update | Description | Release Date | Documentation |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.19. | 2025-07-18 | |
LibraDB kernel version update | The new kernel version 3.2503.1.0 was released for the read-only analysis engine of TencentDB for MySQL. It supported multiple new kernel features. | 2025-07-01 |
June 2025
Update | Description | Release Date | Documentation |
New regions supported by the read-only analysis engine | The Singapore and Chengdu regions were supported for the read-only analysis engine of TencentDB for MySQL. | 2025-06-30 | |
TXSQL kernel feature update | The new kernel version 20250510 was released for TencentDB for MySQL 5.7. | 2025-06-27 | |
LibraDB kernel version update | TencentDB for MySQL released version 2.2410.8.0 with bugs fixed for the read-only analysis engine. | 2025-06-25 | |
LibraDB kernel version update | The new kernel version 2.2410.7.0 was released for the read-only analysis engine of TencentDB for MySQL. It supported multiple new kernel features. | 2025-06-20 | |
Database audit optimization | TencentDB for MySQL optimized the database audit feature as follows: Optimized the interface display after the configuration of log shipping to TDMQ for CKafka was successful. Added PREPARE to the feature string of the parameter field "SQL Type" in the rule content when a rule template was created or modified. Fixed the issue that no audit record could be matched by entering a table name. | 2025-06-09 | |
Update of the CPU elastic scale-out feature | TencentDB for MySQL released a new version of the CPU elastic scale-out feature. It supported automatic and custom CPU scale-out to easily cope with burst load and ensure online business stability. The scale-out methods after the update included automatic scale-out and custom scale-out. Custom scale-out supported setting the scale-out time, which can be Now, By time period, or By cycle. When the scale-out time was set to By time period or By cycle, automatic scale-out could be enabled. The scale-out history could be queried. | 2025-06-05 |
May 2025
Update | Description | Release Date | Documentation |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.17. | 2025-05-13 | |
LibraDB kernel version update | New kernel versions 1.2404.24.0 and 2.2410.6.0 were released for the read-only analysis engine of TencentDB for MySQL. | 2025-05-06 |
April 2025
Update | Description | Release Date | Documentation |
Support for backup retention settings | TencentDB for MySQL supported backup retention settings to prevent accidental instance deletion from causing immediate backup termination. This ensured data traceability and recoverability. | 2025-04-29 | |
Support for configuration adjustment on the read-only analysis engine | Read-only analysis engine instances of TencentDB for MySQL supported adjusting the instance configuration. | 2025-04-27 | |
Support for multi-node high availability on the read-only analysis engine | Read-only analysis engine instances of TencentDB for MySQL supported multi-node high availability capabilities. | 2025-04-27 | |
Support for alarm configuration on the read-only analysis engine | Read-only analysis engine instances of TencentDB for MySQL supported alarm configuration capabilities. | 2025-04-27 | |
LibraDB kernel version update | New kernel versions 1.2404.23.0 and 2.2410.5.0 were released for the read-only analysis engine of TencentDB for MySQL. | 2025-04-22 | |
Database audit optimization | TencentDB for MySQL optimized the database audit feature as follows: Added the display of the generation progress in the audit log file list. Added the options of "All fields" and "Interaction with custom list fields (including field order and content)" when an audit log file was created. Added PREPARE for the SQL type. Optimized the display of source IP addresses for SaaS operations (Data Transfer Service (DTS), DBbrain, and Database Management Center (DMC)). Optimized the display of error codes, transaction IDs, and table names. Added version support descriptions for audit log fields. Optimized the timeout logic for the fuzzy query and wildcard query scenarios. | 2025-04-09 |
March 2025
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | The new kernel version 20250330 was released for TencentDB for MySQL 5.7. | 2025-03-27 | |
Release of two-node economical instances | TencentDB for MySQL supported two-node economical instances. The new architecture provided stable services to meet the business requirements for computing and storage resources and reduce the use costs. Small and medium-sized enterprises and individual developers could use database services that better met their business requirements. | 2025-03-26 | |
LibraDB kernel version update | TencentDB for MySQL released versions 1.2404.22.1 and 2.2410.4.1 with bugs fixed for the read-only analysis engine. | 2025-03-25 | |
LibraDB kernel version update | TencentDB for MySQL released versions 1.2404.22.0 and 2.2410.4.0 with bugs fixed for the read-only analysis engine. | 2025-03-15 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.4.4. | 2025-03-14 | |
Support for shipping database audit logs to TDMQ for CKafka | TencentDB for MySQL supported shipping database audit logs to TDMQ for CKafka. The database audit logs of instances could be collected and shipped to TDMQ for CKafka for real-time stream computing. | 2025-03-12 | |
Support for shipping database audit logs to CLS | TencentDB for MySQL supported shipping database audit logs to Cloud Log Service (CLS). The database audit logs of instances could be collected and shipped to CLS for unified management and analysis. | 2025-03-12 | |
Database audit feature supported by Cluster Edition | Instances of TencentDB for MySQL Cluster Edition supported the database audit feature. After the database audit feature was enabled, users could view audit logs, perform full audit and rule-based audit, search for audit logs, configure post-event alarms, and ship audit logs to TDMQ for CKafka and CLS. | 2025-03-12 | |
TXRocks kernel feature update | The new kernel version 20240702 was released for TencentDB for MySQL 5.7. | 2025-03-11 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.16. | 2025-03-06 |
February 2025
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | The new kernel version 20241001 was released for TencentDB for MySQL 8.0. | 2025-02-18 | |
LibraDB kernel version update | TencentDB for MySQL released version 1.2404.21.0 with bugs fixed for the read-only analysis engine. | 2025-02-12 | |
LibraDB kernel version update | The new kernel version 2.2410.1.0 was released for the read-only analysis engine of TencentDB for MySQL. It supported multiple new kernel features. | 2025-02-05 |
January 2025
Update | Description | Release Date | Documentation |
Beta testing for the read-only analysis engine | The read-only analysis engine feature of TencentDB for MySQL was under beta testing. It significantly improved performance in multiple business scenarios such as complex SQL execution, big data processing, and multi-table joins. It could be widely used in typical scenarios such as slow queries, batch data processing, and reconciliation queries. | 2025-01-21 | |
TXSQL kernel feature update | The new kernel version 20240930 was released for TencentDB for MySQL 8.0. | 2025-01-10 |
December 2024
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | The new kernel version 20230704 was released for TencentDB for MySQL 8.0. | 2024-12-31 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.15. | 2024-12-19 | |
TXSQL kernel feature update | The new kernel version 20230703 was released for TencentDB for MySQL 8.0. | 2024-12-18 | |
TXRocks kernel feature update | The new kernel version 20231030 was released for TencentDB for MySQL 8.0. Added the virtual bulk load feature. Added the LOCK TABLES FOR BACKUP syntax. | 2024-12-03 | |
TXRocks kernel feature update | The new kernel version 20231030 was released for TencentDB for MySQL 5.7. Added the virtual bulk load feature. | 2024-12-03 |
November 2024
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | The new kernel version 20230702 was released for TencentDB for MySQL 8.0 to improve database performance and stability: Reduced the overhead caused by frequent notifying of the exchange operator in parallel queries. Fixed the instance crash issue that occurred when INSTANT DDL was executed to modify the column position. | 2024-11-12 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.14. | 2024-11-08 |
August 2024
Update | Description | Release Date | Documentation |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.13. | 2024-08-26 | |
Database audit optimization | TencentDB for MySQL optimized the database audit feature as follows: Released a new version of the rule-based audit feature. Uniformly changed the unit of the audit log field Execution Time to microseconds in both the console and downloaded audit log files. Added the display of the millisecond-level time for the unit of the Timestamp field in audit log files. Note: The old version of the rule-based audit feature provided on the Audit Rules and Audit Policies pages will be unavailable soon. Adjust and configure the new version of the rule-based audit feature in a timely manner. | 2024-08-09 | |
TXSQL kernel feature update | The new kernel version 20240331 was released for TencentDB for MySQL 5.7 to improve database performance and stability: Incorporated changes from official versions 5.7.36, 5.7.37, 5.7.38, 5.7.39, 5.7.40, 5.7.41, 5.7.42, 5.7.43, and 5.7.44. Added the update returning feature. Added the display of the Data Definition Language (DDL) progress. During the DDL operation period, the show detail processlist command could be executed to view the progress. Added the default table encryption feature. | 2024-08-09 | |
Support for one-click upgrade to Cluster Edition | TencentDB for MySQL supported one-click upgrade of dual-node and three-node instances to Cluster Edition instances. | 2024-08-01 |
July 2024
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | The new kernel version 20230701 was released for TencentDB for MySQL 8.0 to improve database performance and stability: Supported restoring TXSQL physical backups by using the community edition. Replaced all keywords in the AWR feature with TXSQL_AWR. Fixed the issue where the underlying tables failed to open when competition occurred between background threads and RENAME operations on the dict cache. | 2024-07-30 |
June 2024
Update | Description | Release Date | Documentation |
Support for Cluster Edition | The TencentDB for MySQL Cluster Edition architecture was fully released. | 2024-06-28 | |
Update of the Product Pricing page | A new version of the Product Pricing page of TencentDB for MySQL was released, supporting the query and export of prices for different types/architectures and comprehensively covering price query and quotation scenarios. | 2024-06-26 | |
Support for CAM authentication (password-free account login) | TencentDB for MySQL supported enabling the Cloud Access Management (CAM) authentication (password-free account login) feature, helping you simplify the complexity of account permission management, and enhancing database security and account management efficiency. | 2024-06-24 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.12. | 2024-06-14 |
May 2024
Update | Description | Release Date | Documentation |
Database audit optimization | TencentDB for MySQL optimized the database audit feature as follows: Optimized the query time box on the Audit Log page and added quick query time options. Added the Table Name and Transaction ID fields to audit logs. | 2024-05-16 | |
Support for multiple disaster recovery instances | The primary instances with the TencentDB for MySQL two-node or three-node architecture support mounting multiple disaster recovery instances. This enhances business continuity and data reliability. | 2024-05-15 |
April 2024
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | The new kernel version 20230630 was released for TencentDB for MySQL 8.0 to improve database performance and stability: Supported the nonblocking DDL feature. Supported recording the TP/AP load statistics of the largest GTS instance in the relay log for XA commit. Supported selecting InnoDB temporary tables to be shared by parallel query worker threads. Supported using partitioned tables as parallel tables in parallel queries. Supported the flashback version query feature. Supported flashback query persistence. Supported virtual indexes. Supported the range-based/list-based secondary partitioning feature. Supported the feature of automatic relay log recovery. Supported the default algorithm of DDL. INPLACE and INSTANT were optional. Supported Fast Query Cache. Supported the conversion of partitioned tables from MyISAM to InnoDB. | 2024-04-23 |
March 2024
Update | Description | Release Date | Documentation |
Support for Cluster Edition | During the grayscale release of the TencentDB for MySQL Cluster Edition architecture, multiple specific capabilities of Cluster Edition were provided, including automatic failover, switching of any secondary node (read-only node) to a primary node (read-write node), read-only secondary nodes, on-demand node addition and deletion, multi-availability zone (AZ) disaster recovery, node-level monitoring, and node topology management. These features help users handle diverse and complex business scenarios. | 2024-03-26 | |
TXSQL kernel feature update | The new kernel version 20230601 was released for TencentDB for MySQL 5.7 to improve database performance and stability: Supported flashback query persistence. Supported DROP TABLE FORCE to implement dropping InnoDB metadata. Supported Parallel Copy DDL. Supported the LIMIT clause in subqueries. Supported the conversion of partitioned tables from MyISAM to InnoDB. | 2024-03-19 |
February 2024
Update | Description | Release Date | Documentation |
Support for cross-region CLS | TencentDB for MySQL supported shipping slow logs and error logs to cross-region CLS. | 2024-02-26 |
November 2023
Update | Description | Release Date | Documentation |
Support for setting data verification sensitivity | In scenarios where migration and specification changes were triggered due to the configuration adjustment of primary instances of TencentDB for MySQL, data verification sensitivity settings were introduced to control the data verification duration and performance impact. | 2023-11-27 |
October 2023
Update | Description | Release Date | Documentation |
Support for log shipping | TencentDB for MySQL supported shipping slow logs and error logs. It collected the corresponding log data and shipped the data to CLS, achieving rapid monitoring and localization of business issues. | 2023-10-18 | |
Support for upgrading MySQL 5.7 to MySQL 8.0 | TencentDB for MySQL fully supported upgrading MySQL 5.7 to MySQL 8.0. MySQL 8.0 delivered better performance and enhanced features, demonstrating more outstanding performance in high-concurrency and big-data scenarios while providing enhanced system performance and stability. | 2023-10-10 | |
Support for the Frankfurt region for single-node instances | TencentDB for MySQL single-node instances supported the Frankfurt region, offering ultra-high cost-effectiveness and supporting a maximum of 30 TB of storage space. | 2023-10-10 |
September 2023
Update | Description | Release Date | Documentation |
Database audit optimization | TencentDB for MySQL optimized the database audit feature as follows: Supported binding multiple rule templates to instances. Changed the relationship between rule templates and instances from initialization to strong binding. That is, the modification of the content in a rule template would cause a change to the audit rules used for instances bound to the template. Supported viewing the rule templates bound to each instance, the audit rules hit by each audit log, and the instances associated with each rule template. Integrated with EventBridge and Tencent Cloud Observability Platform (TCOP), supporting high, medium, and low-risk event alarms. | 2023-09-25 |
August 2023
Update | Description | Release Date | Documentation |
Transaction-level connection pools supported by the database proxy | The database proxy of TencentDB for MySQL supported transaction-level connection pools, helping enhance database concurrency performance and resource utilization. This avoided competition and conflicts among multiple transactions and improved the concurrency performance and reliability of transaction processing. | 2023-08-25 | |
Optimization of the Instance Details page | The Instance Details page of TencentDB for MySQL was optimized to support viewing the instance health status and abnormal alarms and provide an improved display of instance configurations in terms of availability, performance, and security. | 2023-08-16 | |
Database audit optimization | The Database Audit Log page of TencentDB for MySQL was optimized. SQL command details supported multi-mode search, with matching options including Include/Exclude, OR/AND, and Segment/Wildcard. | 2023-08-09 |
July 2023
Update | Description | Release Date | Documentation |
Support for binlog encryption | TencentDB for MySQL supported binlog encryption to improve data security and reliability. | 2023-07-17 | |
Database audit optimization | The Database Audit Log page of TencentDB for MySQL was optimized. Various search patterns, such as fuzzy, precise, forward, reverse, simple, and complex search patterns, were supported. The units of the audit log fields Execution Time and CPU Time were uniformly changed to microseconds in both the console and downloaded audit log files. | 2023-07-12 |
May 2023
Update | Description | Release Date | Documentation |
Support for performance elastic management | The performance elastic management feature of TencentDB for MySQL was fully released, supporting manual CPU scaling and automatic performance scaling. This better alleviated performance pressure caused by sudden requests, adapted to peak business traffic, and ensured the stability of the online business. | 2023-06-25 | |
Release of the new database audit version | The new database audit version of TencentDB for MySQL was in grayscale release. The new version supported full audit and rule-based audit features. It provided features such as data collection integrity and reliability, data tamper-proofing, data transmission integrity, and data storage integrity. | 2023-05-15 | |
Support for the creation of cross-AZ RO groups | TencentDB for MySQL supported creating cross-AZ read-only (RO) groups. That is, RO groups could reside in a different AZ from the primary instance, enhancing data disaster recovery capabilities. | 2023-05-04 |
March 2023
Update | Description | Release Date | Documentation |
Launch of the new purchase page | The new purchase page of TencentDB for MySQL was released, supporting one-click configuration import and faster specification filtering. This facilitated quick adjustments and purchases based on existing configurations. | 2023-03-16 |
February 2023
Update | Description | Release Date | Documentation |
Support for the monthly configuration of the backup cycle | The backup cycle of automatic backup of TencentDB for MySQL could be set on a monthly basis. That is, the backup cycle supported custom configuration on a weekly or monthly basis for backup time settings. | 2023-02-28 | |
Support for transition-to-cold storage for backup | TencentDB for MySQL supported configuring transition-to-cold storage for backup. The storage type of generated backup files could be transitioned based on policies to reduce backup storage costs. | 2023-02-14 |
December 2022
Update | Description | Release Date | Documentation |
Support for parallel queries | TencentDB for MySQL supported the parallel query capabilities. By leveraging parallel query capabilities, it mobilized multi-core computing resources, significantly reducing the response time for large queries. | 2022-12-22 |
November 2022
Update | Description | Release Date | Documentation |
Release of the new database proxy version | TencentDB for MySQL released a new version of database proxy. It provided robust features including automatic read-write separation, transaction splitting, connection pools, and momentary disconnection protection. It also supported mounting read-only instances across AZs and creating multiple database proxy access addresses to meet various business scenario requirements. | 2022-11-02 |
October 2022
Update | Description | Release Date | Documentation |
Support for backup encryption | TencentDB for MySQL supported the backup encryption feature to enhance data security. By leveraging Key Management Service (KMS) to encrypt backup files, security incidents caused by accidental leakage of backups were prevented. | 2022-10-31 | |
Support for single-node instances | TencentDB for MySQL supported single-node Cluster Edition instances, providing ultra-high cost-effectiveness to meet scenarios such as testing, development, and personal learning. A maximum of 30 TB of storage capacity was supported. | 2022-10-08 |
September 2022
Update | Description | Release Date | Documentation |
Support for parameter modification for read-only instances | TencentDB for MySQL supported modifying parameters for read-only instances to meet parameter configuration requirements of various business scenarios. | 2022-09-19 | |
Support for cross-region backup | TencentDB for MySQL supported cross-region backup to achieve high availability for database recovery. This met feature requirements such as data availability and security, remote backup and recovery, cross-region disaster recovery, long-term data archiving, and regulation. | 2022-09-09 |
July 2022
Update | Description | Release Date | Documentation |
Support for password complexity | TencentDB for MySQL supported the password complexity feature, helping enhance the strength of database access passwords and ensure database security. | 2022-07-20 |
June 2022
Update | Description | Release Date | Documentation |
Infrequent access storage supported by TencentDB for MySQL | Tencent Cloud provided infrequent access storage for TencentDB for MySQL. Users could select appropriate billing based on the actual storage frequency of their database audit, helping reduce the cost of using audit. | 2022-06-30 | |
Support for SSL encryption | TencentDB for MySQL supported Secure Sockets Layer (SSL) encryption to establish a secure encrypted transmission channel. This enhances the security and integrity of communication data. | 2022-06-27 |
April 2022
Update | Description | Release Date | Documentation |
Support for intelligent parameter tuning | TencentDB for MySQL supported the intelligent parameter tuning feature, helping users improve database performance. | 2022-04-25 | |
Support for the TXRocks engine | TencentDB for MySQL supported the TXRocks transactional storage engine, which offers performance comparable to InnoDB while saving more storage space. The TXRocks engine is suitable for businesses that require high transactional read/write performance and large data storage capacity. | 2022-04-18 | |
Support for scheduled backups | Scheduled backups supported backup planning with two scheduling cycles, which were more cost-effective compared to single-cycle backup policies. | 2022-04-02 |
February 2022
Update | Description | Release Date | Documentation |
Connection pools supported by the database proxy | The TencentDB for MySQL database proxy supported the connection pool feature. The supported session-level connection pool could effectively resolve the issue of excessive load on database instances caused by the frequent establishment of new connections for non-persistent connection businesses. | 2022-02 | |
Optimization and update of the database proxy feature | The TencentDB for MySQL database proxy feature was optimized and updated. It supported upgrading kernel minor versions of the database proxy, the network switching feature, and self-service configuration adjustments, delivering enhanced performance and more convenient operations. | 2022-02 |
December 2021
Update | Description | Release Date | Documentation |
Optimization of RO group latency settings | The RO latency configuration of TencentDB for MySQL was changed from instance-level to RO group-level. This resolved conflicts between latency settings and removal policies in RO groups and simplified the latency management of RO instances. When an RO group is accessed through the unified IP address, data access inconsistencies caused by delayed RO instances are eliminated, ensuring data consistency with expectations. | 2021-12 | |
Support for migrating instances to other AZs | TencentDB for MySQL launched the feature of migrating instances to other AZs. This feature implemented nearby access for businesses and resource scale-out, achieving more efficient utilization of resources across different AZs in the same region. | 2021-12 | |
Parameter template and newly purchased instance optimization | TencentDB for MySQL optimized parameter-related capabilities and the instance provisioning process. This optimization included upgrades in capabilities such as parameter template creation, parameter comparison, parameter template application, parameter modification, addition of modifiable parameters, and instance purchase optimizations. | 2021-12 |
August 2021
Update | Description | Release Date | Documentation |
Display of project group information in TencentDB for MySQL audit bills | Project group information corresponding to database instances was displayed in the exported bills. This facilitated classified statistics on bills by project group. | 2021-08 | |
Display of instance names in TencentDB for MySQL audit bills | The Instance ID column in the instance list was changed to the Instance ID/Name column, with instance names displayed to facilitate quick instance location. | 2021-08 | - |
Seven-day retention period supported for TencentDB for MySQL audit logs | When you enabled the audit feature, you could set the log retention period to 7 days. This met requirements in scenarios requiring short-term observation of the operational status and issue analysis for database troubleshooting. You could also change the log retention period of instances for which the audit feature had been enabled to 7 days. | 2021-08 | |
TencentDB for MySQL audit search optimization | Fuzzy search was supported. Multiple SQL types were allowed to be set as filter conditions at the same time. The 24-hour limit was removed from search time ranges. | 2021-08 |
July 2021
Update | Description | Release Date | Documentation |
Support for instant specification changes | TencentDB for MySQL supported instant specification changes. When local resources were sufficient, the adjustment of database configurations would trigger instant specification changes. Instant specification changes did not involve data migration. Therefore, the preparation time was reduced, enabling faster instance specification adjustments. | 2021-07 |
April 2021
Update | Description | Release Date | Documentation |
Support for the database proxy | A database proxy was a network proxy service resided between cloud database services and application services. It was used to proxy all requests when an application service accessed a database. The access address of the database proxy was independent of the original database access address. All requests through the database proxy address were forwarded through the proxy cluster to access the primary and secondary nodes of the database, perform read-write separation, forward read requests to read-only instances, and reduce the load on the primary database. | 2021-04 | |
Description of the inclusion of binlog usage space in the total disk usage space | The write speed of binlog affected database runtime performance. Therefore, TencentDB for MySQL would upgrade the binlog storage to improve the performance and stability of TencentDB for MySQL. This upgrade would migrate the storage medium of the instance binlog to high-performance SSD disks (the storage space of user instances). | 2021-04 | |
Support for setting the local binlog retention period | TencentDB for MySQL supported setting the local binlog retention period in the console. | 2021-04 |
March 2021
Update | Description | Release Date | Documentation |
Product architecture (name) upgrade | The product architecture of TencentDB for MySQL was upgraded to support single-node (formerly Basic Edition), dual-node (formerly High Availability Edition), and three-node (formerly Financial Edition) architectures. The basic, general, and exclusive isolation policies were added. Features of each architecture remained unchanged. | 2021-03 | |
Independent private network addresses supported by read-only instances | Read-only instances supported enabling independent private network addresses and allowed custom modifications of private IP addresses and port numbers. | 2021-03 |
December 2020
Update | Description | Release Date | Documentation |
Support for delayed replication for read-only instances | TencentDB for MySQL supported setting delayed replication for read-only instances and starting or stopping replication. By setting delayed replication (the latency between read-only instances and the primary instance) and choosing to initiate restoration to a specific time point or global transaction identifier (GTID) during the latency period, efficient data rollback and quick fault backtracking could be achieved. | 2020-12 |
November 2020
Update | Description | Release Date | Documentation |
Support for instance cloning | TencentDB for MySQL supported restoring an instance to any time point within the log backup retention period through cloning. It also supported restoration to the backup set of a specified physical backup. | 2020-11 |
October 2020
Update | Description | Release Date | Documentation |
Purchase page optimization | The purchase page of TencentDB for MySQL supported specifying alarm policies, setting parameter templates, and binding security groups across projects. | 2020-10 | |
TDE supported by TencentDB for MySQL 8.0 | TencentDB for MySQL 8.0 supported the Transparent Data Encryption (TDE) feature. | 2020-10 |
August 2020
Update | Description | Release Date | Documentation |
Support for TencentDB for MySQL 8.0 | TencentDB for MySQL 8.0 was supported. This version provided faster and more stable enterprise-level services based on comprehensive management services and the TXSQL kernel. It enriched industry scenarios and facilitated industrial upgrades for customers. | 2020-08 |
July 2020
Update | Description | Release Date | Documentation |
Support for applying parameter templates to instances | TencentDB for MySQL supported modifying parameters of multiple instances at a time by using a parameter template. Parameter modification tasks could be scheduled to run within a custom time period, and these tasks could be canceled. | 2020-07 | |
Support for TDE | TencentDB for MySQL provided the TDE feature. Transparent encryption indicated that the data encryption and decryption operations are invisible to users. It supported real-time I/O encryption and decryption of data files, encrypting data before being written to disks and decrypting data when being read into the memory. This feature met compliance requirements for static data encryption. | 2020-07 | |
Support for the TencentDB for MySQL database audit feature | TencentDB for MySQL provided database audit capabilities to record database accesses and SQL statement execution. This helped enterprises control risks and improved the data security level. | 2020-07 |
June 2020
Update | Description | Release Date | Documentation |
Support for manual upgrade of kernel minor versions | TencentDB for MySQL supported manual upgrade of kernel minor versions, enabling use of new features, performance improvements, bug fixes, and other functionalities. | 2020-06 |
April 2020
Update | Description | Release Date | Documentation |
Renaming High Availability Edition (one primary node and two secondary nodes) Financial Edition | Financial Edition adopted a three-node architecture with one primary node and two secondary nodes. It supported strong synchronous replication. Through real-time hot standby, it ensured strong data consistency while providing finance-grade reliability and high availability. | 2020-04 | |
Support for customizing the reclamation time for old IP addresses | When you switched networks, you could customize the reclamation time for old IP addresses within the range of 0 to 168 hours. If the reclamation time was set to 0 hours, old IP addresses would be reclaimed immediately after the network switch. | 2020-04 |
January 2020
Update | Description | Release Date | Documentation |
Support for DBbrain | DBbrain was a product for intelligent database diagnosis and optimization. It also assisted users in proactive prevention, provided real-time database protection, efficiently identified the causes of failures, and offered corresponding solutions. | 2020-01 | |
Support for slow log details and error log details | TencentDB for MySQL instances (excluding Basic Edition) provided the operation log management feature. On the Operation Logs page in the console, you could view slow log details, error log details, and rollback logs of an instance, and download slow logs. | 2020-01 |
December 2019
Update | Description | Release Date | Documentation |
Commercial charging for TencentDB for MySQL backup | TencentDB for MySQL instance backup space exceeding the free tier would be charged. After backup commercialization, data compression, backup stability, and backup availability were significantly improved, ensuring higher reliability for backups. Users could reduce backup costs by using methods such as shortening the backup retention period and reducing the backup frequency. | 2019-12 |
November 2019
Update | Description | Release Date | Documentation |
Support for event alarms | By subscribing to events such as out of memory (OOM), primary/secondary switching, removal of read-only instances, and instance migration due to server failures, you could be informed about the operation status of your instance in real time. | 2019-11 |
September 2019
Update | Description | Release Date | Documentation |
Launch of the Database Backup page | TencentDB for MySQL has officially launched the Database Backup page, featuring two main sections: Overview and Backup List. The Overview page allows you to conveniently view details and usage trends of backup space, while the Backup List provides a clear display of data backup lists and log backup lists. | 2019-09 |
May 2019
Update | Description | Release Date | Documentation |
Comprehensive upgrade of the backup type from automatic backup to physical backup | TencentDB for MySQL only supported physical backup for automatic backup. Existing instances with logical automatic backup would be automatically switched to physical backup over time. If logical backup was required, you could generate logical backup by using the manual backup feature in the TencentDB for MySQL console or by using API calls. | 2019-05 | |
Support for Nanjing Zone 1 | With the launch of Nanjing Zone 1, TencentDB for MySQL covered two major regions in East China: Shanghai and Nanjing. | 2019-05 |
March 2019
Update | Description | Release Date | Documentation |
Support for switching between VPCs | Switching from VPC A to VPC B was supported. That is, a single cloud database could be switched from VPC A to VPC B. | 2019-03 |
February 2019
Update | Description | Release Date | Documentation |
One-click connection check | The console provided a one-click connection check tool to assist users in quickly locating public and private network connection issues and provide corresponding solutions. | 2019-02 |
June 2018
Update | Description | Release Date | Documentation |
Support for the database audit feature | The database audit feature could record TencentDB operations in real time, perform fine-grained auditing on database operations, report alarms on risky behaviors encountered by databases, and record and report alarms on risky database behaviors such as SQL injection and abnormal operations. | 2018-06 | |
Support for purchasing Basic Edition instances | Basic Edition adopted a single-node deployment mode that separated compute from storage. If a compute node failed, the node could be replace to achieve rapid recovery. The underlying storage medium for MySQL Basic Edition was Premium Cloud Disk, which was suitable for 90% of I/O scenarios. It offered cost-effectiveness and outstanding performance stability. | 2018-06 | |
Support for network switching | Switching from the basic network to a VPC and switching between subnets within a VPC were supported. | 2018-06 | |
Support for self-service connection detection | Self-service connection detection was supported to check whether the database connection was normal. | 2018-06 | |
Support for self-service returns and refunds within 5 days | Each account was eligible for an unconditional full refund within five days (inclusive) from the date of purchase of a newly purchased TencentDB for MySQL yearly/monthly subscription instance. Only one TencentDB for MySQL was eligible for an unconditional full refund within five days (inclusive). | 2018-06 | |
Support for downgrade and refund | Database configurations could be downgraded, and the remaining fees could be returned. | 2018-06 | |
Support for MySQL 5.7 data migration | DTS data migration supported MySQL 5.7. | 2018-06 | |
Product renaming | The product name was renamed from CDB for MySQL to TencentDB for MySQL. | 2018-06 |
August 2017
Update | Description | Release Date | Documentation |
Elastic specifications supported by read-only instances | The specifications of read-only instances no longer needed to be the same as those of the primary instance. | 2017-08 | |
Support for 1-minute monitoring | The 1-minute database monitoring was supported. | 2017-08 | |
Support for physical backup | Data could be stored by using the physical backup. | 2017-08 | |
Support for manual backup | The backup time and storage duration could be customized. The backup retention period could be up to 732 days. | 2017-08 | |
Support for security groups | A security group was a stateful virtual firewall with filtering capabilities. It was used to set network access control for single or multiple cloud databases. It was an important network security isolation mechanism provided by Tencent Cloud. | 2017-08 | |
Support for data subscription | DTS helped users obtain real-time incremental data updates of cloud databases, enabling users to consume incremental data based on their business requirements. | 2017-08 | Data Subscription |
Support for data migration between cloud databases | DTS data migration was compatible with various network environments. | 2017-08 | |
DMC release | DMC supported real-time monitoring and instance session management. | 2017-08 |
June 2017
Update | Description | Release Date | Documentation |
Support for MySQL 5.7 | Based on the MySQL 5.6 kernel, MySQL 5.7 (Percona branch) was added. Building on MySQL 5.7 capabilities, original features such as horizontal scaling and read-write separation were retained. | 2017-06 |
March 2016
Update | Description | Release Date | Documentation |
Launch of read-only instances | TencentDB for MySQL allowed users to create one or multiple read-only instances to support read-write separation and scenarios with one primary node and multiple secondary nodes. This significantly improved read workload capabilities of user databases. | 2016-03 | |
Support for pay-as-you-go instances | Database services were charged on an hourly basis. | 2016-03 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback