MySQL server versions are divided into Innovation track and LTS/BugFix track.

Innovation Track

If you desire access to the latest features and improvements and enjoy staying on top of the latest technologies, then MySQL innovation track is the best fit for you. This is ideal for developers and database administrators working in fast-paced environments with high levels of automated tests and modern continuous integration techniques for faster upgrade cycles. For example, MySQL 8.1.0 is the first innovation release. If you want the latest features, improvements, and all bug fixes for the MySQL database, use the innovation release track, 8.1.x, 8.2.x, 8.3.x, and so on.

LTS/BugFix Track

LTS/Bugfix track contains only necessary fixes, so it is a better choice if your environment requires established database software behavior. Features can be removed and added only in the first version of a LTS release (such as 8.4.0 LTS) but not later versions (such as 8.4.1 LTS and 8.4.2 LTS) in the same LTS release. For MySQL 8.0, 8.0.34 is the first Bugfix version where no features will be removed and added in subsequent versions (such as 8.0.35 and 8.0.36) in the 8.0 release.

Older MySQL versions are marked as deprecated approximately three months before they become unavailable in HeatWave Service. Any DB system running an unavailable version is upgraded automatically in its next maintenance window to the next available version in the same series.

The HeatWave Service begins supporting new MySQL Server versions as soon as they are released as Generally Available (GA).

Customers are advised to regularly update their DB systems to the latest GA version. This can be from either the Innovation or LTS/Bugfix track. Regular updates ensure access to the latest features, bug fixes, and security patches. To update the MySQL Server version of a DB system, see Editing a DB System.

Each MySQL version in the LTS/Bugfix track will be deprecated about one year after its GA date while each MySQL version in the Innovation track will be deprecated about three months after its GA date. A notification banner will appear in the DB system details when you are running a deprecated version of MySQL Server. We strongly recommend updating and testing your DB systems when a MySQL server version has been deprecated.

About three months after the deprecation date, the MySQL server version will be unavailable. Any DB system that is still running an unavailable version will be upgraded automatically in its next maintenance window. It is upgraded to the lowest version currently available in the same series. For example, when version 8.0.31 becomes unavailable, it will be upgraded to 8.0.32 and when version 8.1.0 becomes unavailable, it is upgraded to 8.2.0. If you have configured one or more contacts in the DB system, the contacts will receive a notification about 1 week before the next scheduled maintenance. See Viewing and Managing Contacts.

Each MySQL version is released on its General Availability date and is deprecated before it is made unavailable.

You can retrieve the version of the MySQL server of a DB system by using the Console, CLI, or SQL command.

You can view the MySQL version number of a DB system on the Console from the DB system details page. See Using the Console. The same information is available by running a CLI command to retrieve the DB system details. See Using the CLI. If you want to view the full MySQL version information of the DB system, you must connect to the DB system and run a SQL command.

Use a command-line client such as MySQL Client or MySQL Shell to retrieve the version of a MySQL Server.

1. Connect to the DB system using the command-line client of your choice.
2. Run the following command:

   SELECT @@version;

 SELECT @@version;
+-----------------+
| @@version       |
+-----------------+
| 8.0.34-u1-cloud |
+-----------------+
1 row in set (0.1687 sec)