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 |
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 |
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 |
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 |
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 |
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. |
Was this page helpful?