tencent cloud

Feedback

Database Versions

Last updated: 2024-11-14 16:02:59

    Supported Versions

    TDSQL-C for MySQL supports MySQL 5.7 and MySQL 8.0. For the lifecycle of each version, see Lifetime Support Policy: Coverage of Technology (Oracle MySQL Releases). MySQL's official lifecycle support policies are shown below:
    Release
    GA Date
    Premier Support End
    Extended Support End
    Sustaining Support End
    MySQL Database5.7
    Oct-15
    Oct-20
    Oct-23
    Indefinite
    MySQL Database8.0
    Apr-18
    Apr-25
    Apr-26
    Indefinite
    Note:
    TDSQL-C for MySQL will extend support for MySQL 5.7 until after October 2023. During the extended service period, important patch updates, upgrade capabilities, and service support will still be provided regularly. Tencent Cloud will prioritize the availability, reliability, and security of database services.

    Version Support Policies

    Note:
    The Tencent Cloud support end date indicates that the kernel minor version will no longer be optimized for the database version after this date. Customers who have activated the database version can continue to use it or upgrade to a later version to obtain the optimized features of the latest kernel minor version. For update details of each kernel minor version, see Database Kernel Version Release Notes.
    Version
    Tencent Cloud Support Start Date
    Tencent Cloud Support End Date
    Community Deactivation Date
    MySQL 5.7
    June 2017
    -
    October 2023
    MySQL 8.0
    August 2020
    -
    April 2026

    List of Feature Differences between MySQL 8.0 and MySQL 5.7

    Note:
    The table below only lists some important differences between MySQL 8.0 and MySQL 5.7. For specific differences, see the official documentation.
    Feature
    MySQL5.7
    MySQL8.0
    GRANT ... IDENTIFIED BY PASSWORD syntax
    Supported
    Not supported
    PASSWORD() function, such as SET PASSWORD ... = PASSWORD('auth_string')
    Supported
    Not supported
    Parameters of the SQL_MODE system variable, including DB2, MAXDB, MSSQL, MYSQL323, MYSQL40, ORACLE, POSTGRESQL, NO_FIELD_OPTIONS, NO_KEY_OPTIONS, NO_TABLE_OPTIONS, PAD_CHAR_TO_FULL_LENGTH, and NO_AUTO_CREATE_USER
    Supported
    Not supported
    Automatic sorting by default for the GROUP BY syntax
    Supported
    Not supported
    Encryption and decryption functions such as ENCODE(), DECODE(), ENCRYPT(), DES_ENCRYPT(), and DES_DECRYPT()
    Supported
    Not supported
    Space analysis functions. For details, see the official documentation.
    Supported
    Not supported
    Functions that previously accepted strings or geometric parameters as WKB values but currently do not allow geometric parameters. See the official documentation.
    Supported
    Not supported
    The parser interprets \\N as NULL.
    Supported
    Not supported
    PROCEDURE ANALYSE() function
    Supported
    Not supported
    InnoDB compressed temporary tables
    Supported
    Not supported
    JSON_APPEND() and JSON_MERGE() features
    Supported
    Not supported
    Transaction scheduling first-in-first-out (FIFO) algorithm. See the official documentation.
    Supported
    Not supported
    The undo_truncate_sweep_count, undo_truncate_sweep_usec, undo_truncate_flush_count, and undo_truncate_flush_usec counters
    Supported
    Not supported
    Numerical Data Type ZEROFILL
    Supported
    Not supported
    information_schema_stats_expiry
    Supported
    Not supported
    Query cache
    Supported
    Not supported
    The GLOBAL_VARIABLES, SESSION_VARIABLES, GLOBAL_STATUS, and SESSION_STATUS tables in the INFORMATION_SCHEMA database. See the official documentation.
    Supported
    Not supported
    The INNODB_LOCKS and INNODB_LOCK_WAITS tables in the INFORMATION_SCHEMA database
    Supported
    Not supported
    Parallel query
    Not supported
    Supported
    sort merge join
    Not supported
    Supported
    statement outline
    Not supported
    Supported
    REVOKE supports IF EXISTS and IGNORE UNKNOWN USER options.
    Not supported
    Supported
    Supports Atomic DDL, ensuring that DDL operations are fully committed or rolled back. See the official documentation.
    Not supported
    Supported

    TDSQL-C for MySQL 8.0 Strengths

    Combined with comprehensive management services and the TXSQL kernel, TDSQL-C for MySQL provides faster and more stable enterprise-level services. It applies to various industry scenarios and helps customers upgrade business.
    TXSQL is 100% compatible with MySQL and the widely-used MySQL forks.
    TDSQL-C for MySQL supports three disaster recovery systems including hot standby, cold standby, and cross-AZ switch. It can achieve up to 99.99% service availability and up to 99.9999999% data reliability.
    TDSQL-C for MySQL offers a series of easy-to-use database management services, including monitoring, backup, rollback, auto scaling, auditing, and intelligent diagnosis and optimization. With these services, you can focus more on your business development.
    A TDSQL-C for MySQL instance can handle up to million-scale QPS, greatly simplifying business development and database operations. TDSQL-C for MySQL reduces the complexity of business architectures, making it easy for you to manage databases.
    It offers rich instance types, including provisioned resources, Serverless single-node instances (with high availability), and Serverless cluster instances.

    Feature Comparison between TDSQL-C for MySQL 8.0 and Oracle MySQL 8.0

    Feature
    TDSQL-C for MySQL 8.0
    Oracle MySQL 8.0
    Cost performance
    1. Elastic resources.
    2. Tencent's kernel TXSQL.
    3. Integrated backup and restoration.
    4. A complete set of SaaS tools and services.
    1. Huge one-time investment cost.
    2. The open source version has no performance optimization.
    3. Separate deployment of backup resources with additional costs.
    4. Public network traffic fees and high domain name fees.
    Availability
    1. A complete high-availability (HA) switchover system.
    2. Automatic load balancing for the traffic of read-only instances.
    3. Cross-region backup and remote disaster recovery.
    1. You need to buy servers and wait for the delivery.
    2. You need to deploy the high availability and load balancing systems by yourself.
    3. You need to build data centers in multiple regions with high costs.
    Reliability
    1. Data reliability of up to 99.9999999%.
    2. Low RPO and RTO.
    3. Stable primary-secondary data replication.
    1. Data reliability of 99%, which depends on the damage probability of a single disk.
    2. You need extra R&D investment to achieve a low RPO.
    3. Data replication delays or interruptions may occur.
    Ease of use
    1. A complete set of database management services are provided and databases can be easily operated in the console.
    2. Second-level monitoring and intelligent alarms.
    3. Automatic cross-AZ high-availability capability.
    1. You need to deploy high-availability backup and restoration systems by yourself, which requires time and money.
    2. You need extra investment to purchase a monitoring system.
    3. You need to set up data centers in different regions with high costs and Ops labor investment.
    4. The version upgrade cost is high and the maintenance needs a long downtime.
    Performance
    1. Compute and storage resources are separated. The maximum storage capacity of a single cluster is 400 TB.
    2. The optimized TXSQL ensures high performance.
    3. DBbrain supports the intelligent diagnosis and optimization of MySQL.
    1. Oracle MySQL has a slower hardware iteration speed than that of cloud computing, usually resulting in lower performance.
    2. It is costly as database maintenance relies on senior DBAs.
    3. It does not have native performance tools, so you have to purchase or deploy them additionally.
    Security
    1. Prevention in advance by allowlists, security groups, and VPC-based isolation.
    2. SQL auditing after the database operations.
    3. TDSQL-C for MySQL is updated right after the Oracle MySQL has security updates.
    1. The cost of the allowlist configuration is high and the private network needs to be deployed by yourself.
    2. You need to implement encryption by yourself during the database operations.
    3. It is difficult to perform SQL auditing after the database operations as the open-source MySQL does not support SQL auditing.
    4. After MySQL is updated, Ops personnel will be required to install updates or databases will have to be shut down for maintenance.

    Performance Comparison between TDSQL-C for MySQL 8.0 and Oracle MySQL 8.0

    Read Performance

    

    Write Performance

    

    FAQs

    What will happen to TDSQL-C for MySQL after the MySQL Community Edition is deactivated?

    After the MySQL Community Edition is deactivated, TDSQL-C for MySQL will continue to make security fixes for the database version during the extended service cycle, but will only fix major bugs and security issues. It will also continue to perform regular maintenance on hosts, OS, containers, and other service-related components. If you encounter issues related to technical support for the TDSQL-C for MySQL database version, we may be unable to provide relevant technical support, and you will need to upgrade the database version to receive effective technical support services. Note that the SLA only applies to issues related to TDSQL-C for MySQL services but does not cover any failures caused by bugs related to the database engine.

    How do I upgrade the database version?

    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support