Upgrading MySQL 5.7 to MySQL 8.0 on Microsoft Azure Database for MySQL: An Enterprise Guide

The clock is ticking on Azure Database for MySQL 5.7. Due to customer demand, Microsoft has chosen to extend the original end of life date from October 21, 2023 to September 2024 for Azure Database for MySQL – Single Servers and September 2025 for Flexible Servers.

While you have more time to plan, it’s essential that you set the wheels in motion now. Here’s what you need to know to successfully upgrade MySQL 5.7 to MySQL 8.0 on Azure Database for MySQL.

Decide Whether to Upgrade Directly to MySQL 8.0 or Buy More Time with Azure Database for MySQL – Flexible Server

In an ideal world, your organization would be able to upgrade directly to MySQL 8.0. Sometimes, your mission-critical applications simply need more time for refactoring so they work properly with the new database version.

If your MySQL 5.7 databases are on Azure Database for MySQL – Single Server, another cloud, or on-premises, you can buy two more years to plan your upgrade by migrating to Flexible Server. However, keep in mind that you lose out on the potential opportunities that a MySQL 8.0 upgrade could provide during this timeframe.

Planning for MySQL 5.7 to MySQL 8.0 Azure Database for MySQL Upgrades

The number one most important thing to remember when upgrading to MySQL 8.0 is that rolling back to 5.7 (or even a previous minor 8.x release) is not supported. You need a working backup taken before your upgrade attempt to be able to restore the database if something goes wrong.

Preparing for the Transition to MySQL 8.0

Go through a database assessment to see if your Azure Database for MySQL 5.7 databases have any problems that need fixed before you continue forward. Some areas to take a look at include:

• Current environment details and usage.
• High availability requirements.
• Application compatibility and potential code changes.
• Recent performance issues.
• Storage engine changes.
• Authentication changes.

Understand Your Azure MySQL Tool Options

Utilize the MySQL upgrade checker utility to generate compatibility reports for MySQL 5.7. This utility will identify any deprecated features or configurations that need adjustment to ensure smooth operation in MySQL 8.0.

Furthermore, note that not all versions of MySQL 5.7 can be directly upgraded to MySQL 8.0. Your databases must be on MySQL 5.7.9 to enable a direct upgrade path to 8.0. If you are running earlier versions of 5.7, you must first upgrade to 5.7.9 before proceeding to 8.0.

Azure provides several migration tools, such as the Azure Database Migration Service (DMS) and MySQL Workbench, to facilitate the migration process from MySQL 5.7 to 8.0. These tools handle schema conversion, data transfer, and compatibility analysis to assist in resolving any issues.

Thorough Testing is Crucial

Conduct exhaustive testing of your applications and databases to ensure their functionality and performance. Deploying MySQL 8.0 databases in a production environment without thorough testing may lead to application errors and unresponsive databases.

Allocate Sufficient Upgrade Time

Don’t leave your team rushing to finish the Azure Database for MySQL 8.0 upgrade in a maintenance window that’s too short. Ensure that they have the time and resources needed to get everything handled.

Allow ample time to double-check for any issues as you transition to the production environment, so you can promptly address any unexpected problems within your scheduled maintenance window.

Schedule the maintenance window to minimize disruption to your users and systems during the upgrade process. Communicate the planned downtime to all stakeholders and ensure they are aware of the expected duration and potential impacts on their operations.

Upgrading from MySQL 5.7 to MySQL 8.0 on Azure empowers your organization with improved performance, enhanced security, and new features. Learn more about MySQL 5.7 to 8.0 upgrade planning in our white paper, How to Plan a MySQL 5.7 to MySQL 8.0 Upgrade Before End of Life.