TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
Release Notes
Last updated: 2025-01-07 14:48:36
December 2024
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | TencentDB for MySQL 8.0 kernel version updated 20230704. | 2024-12-31 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.15. | 2024-12-19 | |
TXSQL kernel feature update | TencentDB for MySQL 8.0 kernel version updated 20230703. | 2024-12-18 | |
TXRocks kernel feature update | TencentDB for MySQL 8.0 kernel version updated 20231030. Added virtual bulk load function. Introduced the "LOCK TABLES FOR BACKUP" syntax. | 2024-12-03 | |
TXRocks kernel feature update | TencentDB for MySQL 5.7 kernel version updated 20231030. Added virtual bulk load function. | 2024-12-03 |
November 2024
Update | Description | Release Date | Documentation |
TXSQL kernel feature update | TencentDB for MySQL 8.0 kernel version updated 20230702 to enhance database performance and stability: Reduced the overhead caused by frequent notifying of parallel query exchange operators. Fixed the abnormal issue of the instance crash caused by an instant DDL's modifying a 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 was optimized for database audit as follows. Released a new version of rule auditing. The Execution Time field in audit logs was uniformly adjusted to microseconds in both the console and downloaded audit log files. Added the display unit of milliseconds to the Timestamp field in audit log files. Note: The earlier version of rule auditing provided on the Audit Rules and Audit Policies pages is about to be deprecated. Make adjustments and configure the new version of rule auditing in a timely manner. | 2024-08-09 | |
TXSQL kernel feature updates | Updated the kernel version 20240331 of TencentDB for MySQL 5.7 to improve database performance and stability: Merged official 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 changes. Added the update returning feature. Added a DDL progress display. During DDL operations, the show detail processlist command can be run to view it. Added the default table encryption feature. | 2024-08-09 | |
Support of one-click upgrade to cluster edition | TencentDB for MySQL supports a one-click upgrade from dual-node and three-node instances to cluster instances. | 2024-08-01 |
July 2024
Update | Description | Release Date | Documentation |
TXSQL kernel feature updates | Updated the kernel version 20230701 of TencentDB for MySQL 8.0 to improve database performance and stability: Supports initiating TXSQL physical backup using the community version. Replaced all keywords in the AWR feature with "TXSQL_AWR". Fixed an issue where the background thread competing with RENAME on the dict cache could cause a failure to open the underlying table. | 2024-07-30 |
June 2024
Update | Description | Release Date | Documentation |
Support of cluster edition | The architecture of the TencentDB for MySQL cluster edition was fully released. | 2024-06-28 | |
Product pricing page update | TencentDB for MySQL released a new version of the product pricing page, supporting the querying and exporting of prices for different types/architectures and fully covering price inquiry and quotation scenarios. | 2024-06-26 | |
Support of CAM authentication (passwordless account login) | TencentDB for MySQL supports enabling the CAM authentication (passwordless account login) feature for accounts, which helps you simplify the complexity of account permission management and enhance the security of the database and the efficiency of account management. | 2024-06-24 | |
Database proxy version update | TencentDB for MySQL released database proxy version 1.3.12. | 2024-06-14 |
May 2024
Product Name | Product Description | Release Time | Relevant Documentation |
Database Audit Optimization | TencentDB for MySQL has made the following optimizations for database auditing. Optimized the query time column in audit logs page, and added quick time query. Added fields "Table Name", "Transaction ID" in audit logs. | May 16, 2024 | |
Support for Multiple Disaster Recovery | The primary instance of TencentDB for MySQL dual node and three-node architectures supports mounting multiple disaster recovery instances, helping to enhance business continuity service capability and data reliability. | May 15, 2024 |
April 2024
Product Name | Product Description | Release Time | Relevant Documentation |
TXSQL Kernel Feature Updates | TencentDB for MySQL 8.0 kernel version update 20230630, enhancing database performance and stability: Supports Nonblocking DDL feature. Supports xa commit to record the maximum gts instance TP/AP load statistics in relay log. Supports selecting Innodb temporary tables for parallel query of worker thread sharing. Supports using partition tables as parallel tables for parallel queries. Supports the flashback version query feature. Supports persistence for flashback query. Supports virtual indexes. Supports the range/list secondary partition feature. Supports the automatic relay log recovery feature. Supports the default algorithm for DDL, with options INPLACE/INSTANT. Supports Fast Query Cache. Supports the conversion of partition tables from MyISAM to InnoDB. | April 23, 2024 |
March 2024
Product Name | Product Description | Release Time | Relevant Documentation |
Supports Cluster Edition | TencentDB for MySQL Cluster Edition is undergoing gray release, providing multiple specific capabilities of the Cluster Edition, including automatic failover, any standby node (read-only node) switched to a primary node (read-write node), standby node read-only, on-demand node addition or deletion, multi-AZ disaster recovery, node granularity monitoring, cluster node topology management, etc., to help users cope with complex business scenarios. | March 26, 2024 | |
TXSQL Kernel Feature Updates | TencentDB for MySQL 5.7 kernel version update 20230601, enhancing database performance and stability: Supports persistence for flashback query. Supports drop table force, enabling drop innodb metadata. Supports Parallel Copy DDL. Supports limit in subquery. Supports the conversion of partition tables from MyISAM to InnoDB. | March 19, 2024 |
February 2024
Product Name | Product Description | Release Time | Relevant Documentation |
Supports remote CLS. | TencentDB for MySQL supports shipping slow logs and error logs to remote Cloud Log Service (CLS). | February 26, 2024 |
November 2023
Product Name | Product Description | Release Time | Relevant Documentation |
Supports setting data validation sensitivity. | In the scenario where configuration adjustments on the TencentDB for MySQL primary instance trigger migration configuration change, a new capability to set data validation sensitivity is added, allowing for the control over the validation duration and its performance impact. | November 27, 2023 |
October 2023
Product Name | Product Description | Release Time | Relevant Documentation |
Support for Log Shipping | TencentDB for MySQL supports the shipping of slow logs and error logs, which achieves rapid monitoring and swift identification of business issues by collecting and shipping corresponding log data to CLS. | October 18, 2023 | |
Supports upgrading from MySQL 5.7 to 8.0. | TencentDB for MySQL fully supports upgrading from MySQL 5.7 to 8.0. MySQL 8.0 achieves significant improvements and enhancements in both performance and features, especially in high concurrency and large data volume scenarios, providing stronger system performance and stability. | October 10, 2023 | |
New Support for Single-node in Frankfurt | TencentDB for MySQL single node instance is now supported in the Frankfurt region, offering extremely high cost-performance ratio, with support for up to 30T of storage space. | October 10, 2023 |
September 2023
Product Name | Product Description | Release Time | Relevant Documentation |
Database Audit Optimization | TencentDB for MySQL has made the following optimizations for database auditing. Supports binding multiple rule templates to an instance. The relationship between rule templates and instances has been changed from "Initialization" to "Strong Binding", meaning that modifications to a rule template's content will immediately affect the audit rules applied to instances bound to that template. Supports viewing the rule templates bound to each instance, the audit rules hit by each audit log, and the instances associated with each rule template. Integrates with event bus and TCOP, and supports event alarms for high, medium, and low-risk levels. Rule audit, setting of risk levels and alarm policies and post-event alarms need to submit tickets for usage. | September 25, 2023 |
August 2023
Product Name | Product Description | Release Time | Relevant Documentation |
The database proxy supports the transaction-level connection pool. | The TencentDB for MySQL database proxy supports the transaction-level connection pool feature, which helps enhancing the database's concurrency performance and resource utilization rate, avoiding competition and conflict among multiple transactions, and improving the concurrency performance and reliability of transaction processing. | August 25, 2023 | |
Optimize Instance Detail Page | TencentDB for MySQL has optimized the instance detail page, supporting viewing instance health status, abnormal alarms, and adding configuration displays in terms of availability, performance, and security. | August 16, 2023 | |
Optimize Database Audit | TencentDB for MySQL has optimized the database audit log page, with SQL command details supporting multi-mode search. The matching items include "Including, excluding", "OR, AND", "segmentation, Wildcard". | August 9, 2023 |
July 2023
Update | Description | Release Date | Documentation |
Supported binlog encryption | TencentDB for MySQL supports binlog encryption, enhancing security and reliability of data. | 2023-07-17 | |
Optimized the database audit | TencentDB for MySQL has optimized the audit log page and added multiple search modes,such as fuzzy/exact/forward/reverse/simple/complex search. The units of the audit log fields "Execution Time" and "CPU Time" in the console and downloaded audit log files are all adjusted to microseconds. | 7/12/2023 |
May 2023
Update | Description | Release Date | Documentation |
Supported elastic performance management | Elastic performance management is fully launched for TencentDB for MySQL. It supports manual expansion and automatic scaling to better alleviate the performance pressure caused by sudden requests and adapt to business peaks traffic, ensuring the stability of online business. | 6/25/2023 | |
Launched a new version of database audit | The new audit service of TencentDB for MySQL is in beta test. It supports both full and rule-based audit. The service can protect your data from tampering and ensure its integrity and reliability during collection, transfer, and storage. | 5/15/2023 | |
Supported creating a cross-AZ read-only group | TencentDB for MySQL supports creating read-only (RO) groups across AZs, which means that the RO group instance and the source instance can be deployed in different AZs. In this way, the disaster recovery capability can be enhanced. | 5/4/2023 |
March 2023
Update | Description | Release Date | Documentation |
Launched a new purchase page | TencentDB for MySQL has released a new version of the purchase page, which supports fast import of configurations and faster filtering of specifications. This makes it easier for you to quickly adjust and purchase the specifications based on existing configurations. | 3/16/2023 |
February 2023
Update | Description | Release Date | Documentation |
Supported setting the backup cycle by month | TencentDB for MySQL allows you to configure automatic backup by week or month. | 2/28/2023 | |
Supported transition-to-cold storage | TencentDB for MySQL allows you to configure transition-to-cold storage policies to transition the storage types of generated backup files and reduce the backup storage costs. | 2/14/2023 |
December 2022
Update | Description | Release Date | Documentation |
Supported parallel query | TencentDB for MySQL supports parallel query, which schedules and leverages multiple compute resources to greatly shorten the response time of large queries. | 12/22/2022 |
November 2022
Update | Description | Release Date | Documentation |
Launched a new version of database proxy | TencentDB for MySQL has released a new version of database proxy. It provides powerful features such as automatic read/write separation, transaction split, connection pool, and disconnection prevention. It also supports mounting read-only instances across AZs and enabling multiple database proxy access addresses to meet the requirements in different business scenarios. | 11/2/2022 |
October 2022
Update | Description | Release Date | Documentation |
Supported backup encryption | TencentDB for MySQL supports backup encryption to help improve the data security. Combined with KMS to encrypt backup files, it helps prevent accidental backup leakage from causing security incidents. | 10/31/2022 | |
Supported the single-node architecture | TencentDB for MySQL supports single-node instance of cloud disk edition, which offers a storage space of up to 30 TB and is extremely cost-effective and suitable for diversified scenarios such as testing, development, and learning. | 10/8/2022 |
September 2022
Update | Description | Release Date | Documentation |
Supported parameter modification for read-only instances | TencentDB for MySQL supports modifying read-only instance parameters to meet the parameter configuration needs in different business scenarios. | 9/19/2022 | |
Supported cross-region backup | TencentDB for MySQL supports cross-region backup to ensure the high availability, security, and recoverability of data and implement various features, such as remote backup and restoration, remote disaster recovery, long-term data archive, and regulatory compliance. | 9/9/2022 |
July 2022
Update | Description | Release Date | Documentation |
Supported password complexity | TencentDB for MySQL allows you to set the password complexity to improve the strength of database access passwords and ensure the database security. | 7/20/2022 |
June 2022
Update | Description | Release Date | Documentation |
TencentDB for MySQL supported infrequent access storage | Tencent Cloud provides the infrequent access storage option for TencentDB for MySQL. You can select a suitable storage type based on your actual storage frequency to reduce audit costs. | 6/30/2022 | |
Supported SSL encryption | TencentDB for MySQL supports SSL encryption to create encrypted data transfer channels and thus improve the security and integrity of communication data. | 6/27/2022 |
April 2022
Update | Description | Release Date | Documentation |
Supported intelligent parameter tuning | TencentDB for MySQL supports the intelligent parameter tuning feature to help you improve the database performance. | 4/25/2022 | |
Supported the TXRocks engine | TencentDB for MySQL supports the TXRocks transactional storage engine, which has a performance comparable to that of InnoDB but requires a much smaller storage space. It is suitable for businesses with a large data volume and high requirements for the transactional read/write performance. | 4/18/2022 | |
Supported archive backup | You can use the archive backup feature to back up data by scheduling two cycles, which reduces the costs compared with a single-cycle backup policy. | 4/2/2022 |
February 2022
Update | Description | Release Date | Documentation |
Supported connection pool for the database proxy | The TencentDB for MySQL proxy supports the session-level connection pool. It can effectively solve the problem of excessively high database instance loads caused by frequent establishment of new connections in non-persistent connection businesses. | 2022-02 | |
Optimized and updated the database proxy feature | TencentDB for MySQL's database proxy feature is optimized and updated. It can now support the upgrade of proxy kernel minor version, network switch, and reconfigurations, which delivers a higher convenience and performance. | 2022-02 |
December 2021
Update | Description | Release Date | Documentation |
Optimized RO group delay settings | RO delay configuration in TencentDB for MySQL is moved from instance configuration to RO group configuration, so that delay and removal policies configured in the same RO group will not conflict with each other. Moreover, RO instance delay management is simplified. When an RO group is used to unify IP access, no inconsistency between the accessed and expected data will occur due to a delayed RO instance. | 2021-12 | |
Supported AZ migration | TencentDB for MySQL launched AZ Migration It can implement nearby access and resource expansion for your business and better utilize resources in different AZs in the same region. | 2021-12 | |
Parameter Template and Instance Purchase Process Optimization | TencentDB for MySQL optimizes parameter-related features and instance delivery process, including creating and applying parameter templates, comparing parameters, modifying modifiable parameters, and purchasing instances. | 2021-12 |
August 2021
Update | Description | Release Date | Documentation |
Displayed project group information in bills in MySQL audit | Exported bills display the project group information of database instances for you to categorize bills and collect statistics by project group. | 2021-08 | |
Displayed the instance name in MySQL audit | The original “Instance ID” column in the instance list is changed to “Instance ID/Name” to add the instance name for locating instances more quickly. | 2021-08 | - |
Supported seven days as the log retention period in MySQL audit | When audit is newly enabled, you can set the log retention period to seven days. This is suitable for scenarios where you want to observe execution conditions and analyze discovered database problems for a short time. For instances with audit already enabled, you can also change the log retention period to seven days. | 2021-08 | |
Optimized search in MySQL audit | Fuzzy search is supported, multiple SQL types can be used together for filtering, and the 24-hour limit on the search time period is removed. | 2021-08 |
July 2021
Update | Description | Release Date | Documentation |
Supported QuickChange | TencentDB for MySQL now supports QuickChange. If the physical machine where the instance is deployed has sufficient resources (aka local resources), you can adjust instance configuration in the QuickChange mode without migrating data. As it takes less time for preparation, the overall adjustment process becomes faster. | 2021-07 |
April 2021
Update | Description | Release Date | Documentation |
Supported database proxy | Database proxy is a network proxy service between the TencentDB service and the application service. It is used to proxy all requests when the application service accesses the database. The database proxy access address is independent of the original database access address. Requests proxied at the proxy address are all relayed through the proxy cluster to access the source and replica nodes of the database. Read/Write separation is implemented, so that read requests are forwarded to read-only instances, which lowers the load of the source database. | 2021-04 | |
Notice on Binlog Taking up the Disk Space | As the speed of writing to binlog affects database performance, TencentDB for MySQL now migrates the binlog files to high-performance SSDs (i.e., instance disk space) in order to improve database performance and stability. | 2021-04 | |
Local binlog retention period can be customized | You can now customize the retention period of local binlog files in the TencentDB for MySQL console. | 2021-04 |
March 2021
Update | Description | Release Date | Documentation |
Instance architectures have been renamed | TencentDB for MySQL now supports three types of architectures including single-node (formerly Basic Edition), two-node (formerly High-Availability Edition), and three-node (formerly Finance Edition), and three resource isolation policies including basic, general, and dedicated policies. Renaming won't change any features of these architectures. | 2021-03 | |
Read-only instances support exclusive private network addresses | You can now configure a custom and exclusive private network address (IP and port) for a read-only instance. | 2021-03 |
December 2020
Update | Description | Release Date | Documentation |
Supported delayed replication for read-only instances | TencentDB for MySQL allows you to set delayed replication for read-only instances and enable/disable replication. You can set delayed replication (i.e., delay between a read-only instance and its source instance) and select to replay by flashbacked position or global transaction identifier (GTID) during the delay to efficiently roll back data and fix failures. | 2020-12 |
November 2020
Update | Description | Release Date | Documentation |
Instances can be cloned | You can now restore a TencentDB for MySQL instance to any point in time within the log backup retention period or from a specific physical backup set by cloning. | 2020-11 |
October 2020
Update | Description | Release Date | Documentation |
The purchase page is optimized | You can now specify alarm policies, parameter templates, and bind an instance with security groups of other projects on the purchase page. | 2020-10 | |
TDE is supported for MySQL 8.0 | TencentDB for MySQL 8.0 now supports Transparent Data Encryption (TDE). | 2020-10 |
August 2020
Update | Description | Release Date | Documentation |
Supported MySQL 8.0 | TencentDB for MySQL 8.0 is now supported. Combined with a complete set of management services and the TXSQL kernel, TencentDB for MySQL provides an enterprise-grade database service that is more stable and quicker to deploy. It applies to various use cases and helps you upgrade your business. | 2020-08 |
July 2020
Update | Description | Release Date | Documentation |
Parameter templates can be applied to instances | TencentDB for MySQL supports modifying parameters of multiple instances at the same time through parameter templates. You can perform a parameter modification task during the custom time window, or cancel it. | 2020-07 | |
Supported transparent data encryption (TDE) | TencentDB for MySQL comes with the transparent data encryption (TDE) feature. Transparent encryption means that the data encryption and decryption are transparent to users. TDE supports real-time I/O encryption and decryption of data files. It encrypts data before it is written to disk, and decrypts data when it is read into memory from disk, which meets the compliance requirements of static data encryption. | 2020-07 | |
Supported MySQL database audit | Tencent Cloud provides database audit capabilities for TencentDB for MySQL, which can record accesses to databases and executions of SQL statements to help you manage risks and improve the database security. | 2020-07 |
June 2020
Update | Description | Release Date | Documentation |
Supported manual kernel minor version upgrade | TencentDB for MySQL supports manual kernel minor version upgrade. Upgrading adds new features, improves performance, and fixes issues. | 2020-06 |
April 2020
Update | Description | Release Date | Documentation |
One-source-two-replica High-Availability Edition is renamed as Finance Edition | The Finance Edition adopts a one-source-two-replica architecture (three nodes in total) and supports strong sync replication. It guarantees strong data consistency through real-time hot backup and provides finance-grade reliability and high availability. | 2020-04 | |
Repossession time for the old IP address can be customized | The repossession time of the old IP address can be customized between 0 and 168 hours when the network is switched. If the repossession time is set to 0 hours, the old IP address will be repossessed immediately after the network switch. | 2020-04 |
January 2020
Update | Description | Release Date | Documentation |
Supported TencentDB for DBbrain | TencentDB for DBbrain (DBbrain) is an intelligent database diagnosis and optimization product. It provides real-time database protection, locates causes of and offers solutions to database exceptions, and helps with exception prevention at the source. | 2020-01 | |
Slow log and error log details can now be queried | TencentDB for MySQL (excluding the Basic Edition) instances support operation log management. In the Operation Log tab, you can view the slow logs details, error logs details, and rollback logs of the instance and download slow logs. | 2020-01 |
December 2019
Update | Description | Release Date | Documentation |
MySQL backup is now a paid service | TencentDB for MySQL will start charging for the usage of instance backup space exceeding the free tier. Improvements will be made for data compression, backup stability and availability. You can shorten retention periods and lower backup frequencies to reduce your backup capacity costs. You can shorten retention periods and lower backup frequencies to reduce your backup capacity costs. | 2019-12 |
November 2019
Update | Description | Release Date | Documentation |
Supported event alarming | By subscribing to events such as OOM, source-replica switch, read-only instance removal, and instance migration caused by server failure, you can now stay on top of your instance statuses. | 2019-11 |
September 2019
Update | Description | Release Date | Documentation |
Database backup page is available | We have released the TencentDB for MySQL database backup page. It is divided into two sections: overview and backup list. Backup trends and statistics can be viewed in the overview tab. Backup data details and log backups can be found in the backup list. | 2019-09 |
May 2019
Update | Description | Release Date | Documentation |
Automatic backups are fully upgraded to physical backup | The automatic backup feature of TencentDB for MySQL only supports physical backup. Existing automatic logical backups will be switched to physical backups. If you need logical backups, you can use the manual backup feature in the TencentDB for MySQL console or call APIs. | 2019-05 | |
Nanjing Zone 1 is now available | TencentDB for MySQL is now available in Nanjing Zone 1. With this new AZ, TencentDB for MySQL is now available in two regions in East China: Shanghai and Nanjing. | 2019-05 |
March 2019
Update | Description | Release Date | Documentation |
Supported switching between VPCs | Switch from VPC A to VPC B: A single TencentDB instance can be switched from VPC A to VPC B. | 2019-03 |
February 2019
Update | Description | Release Date | Documentation |
Supported one-click connectivity check | A one-click connectivity check is now provided in the console to help you quickly locate internal and external connectivity problems and offer corresponding solutions. | 2019-02 |
June 2018
Update | Description | Release Date | Documentation |
Supported database audit | Database audit can record the actions of TencentDB in real time. It carries out fine-grained audit on database operations, records and alerts such risky database behaviors as SQL injection and abnormal operation. | 2018-06 | |
Supported purchasing Basic Edition instances | TencentDB for MySQL Basic Edition adopts a single-node deployment method with computation-storage separation. If a computing node fails, the system can switch to a healthy one for quick recovery. Premium cloud disks are used as the underlying storage media of the Basic Edition, which feature high quality, cost-effectiveness, stability, and performance, making them suitable for 90% of I/O scenarios. | 2018-06 | |
Supported network switch | Switching between the classic network and VPC and between subnets in the same VPC is now supported. | 2018-06 | |
Supported self-service connectivity check | You can now quickly check the connectivity status of your databases. | 2018-06 | |
Supported 5-day self-service return and refund | TencentDB for MySQL allows you to return one monthly subscribed instance unconditionally within five (inclusive) days after purchase under each account. | 2018-06 | |
Supported downgrading and refunding | You can now downgrade your database configuration and be refunded accordingly. | 2018-06 | |
Supported MySQL 5.7 data migration | DTS now supports migrating MySQL 5.7. | 2018-06 | |
Product is renamed | CDB for MySQL is renamed TencentDB for MySQL. | 2018-06 |
August 2017
Update | Description | Release Date | Documentation |
Elastic specifications is supported for read-only instances | A read-only instance can now adopt a different specification from that of its source instance. | 2017-08 | |
Monitoring at a 1-minute granularity is now supported | Monitoring can now be performed at a 1-minute granularity. | 2017-08 | |
Supported physical backup | Data can now be stored through physical backups. | 2017-08 | |
Supported manual backup | You can now customize the backup time and retention period (up to 732 days). | 2017-08 | |
Supported security group | Security group serves as a stateful virtual firewall with filtering feature for configuring network access control for one or more TencentDB instances. It is an important network security isolation tool provided by Tencent Cloud. | 2017-08 | |
Supported data subscription | DTS can now help you get incrementally updated data in TencentDB in real time, so that you can consume incremental data based on your business needs. | 2017-08 | Data Subscription |
Supported data migration between TencentDB instances | DTS is now compatible with more types of network environments. | 2017-08 | |
Data Management Center (DMC) is available | DMC supports real-time monitoring and management of instance sessions. | 2017-08 |
June 2017
Update | Description | Release Date | Documentation |
Supported MySQL 5.7 | MySQL 5.7 (Percona server) is now supported as well as MySQL 5.6 kernel. Native capabilities such as horizontal scaling and read/write separation are also supported. | 2017-06 |
March 2016
Update | Description | Release Date | Documentation |
Read-only instance feature is available | TencentDB for MySQL allows you to create one or more read-only instances, which are suitable for read/write separation and one-source-multiple-replica application scenarios and capable of greatly enhancing the read load capacity of your database. | 2016-03 | |
Supported pay-as-You-Go instances | Database services can now be billed by hour. | 2016-03 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No