Skip to content

Commit 88a8368

Browse files
authored
Update how-to-upgrade.md
1 parent 5e7dc85 commit 88a8368

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

articles/mysql/flexible-server/how-to-upgrade.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,15 @@ To perform a major version upgrade for an Azure Database for MySQL Burstable SKU
5656

5757
Before proceeding with the upgrade, run Oracle's official tool to validate that your current database schema is compatible with MySQL 8.0. This step is crucial to ensure a smooth upgrade process.
5858

59-
4. Pre-Upgrade Decision
59+
>[!NOTE]
60+
>When you use Oracle's official tool to check schema compatibility, you might encounter some warnings indicating unexpected tokens in stored procedures, such as:
61+
>`mysql.az_replication_change_master - at line 3,4255: unexpected token 'REPLICATION'`
62+
>`mysql.az_add_action_history - PROCEDURE uses obsolete NO_AUTO_CREATE_USER sql_mode`
63+
>You can safely ignore these warnings. They refer to built-in stored procedures prefixed with mysql., which are used to support Azure MySQL features. These warnings do not affect the functionality of your database.
64+
65+
66+
67+
5. Pre-Upgrade Decision
6068

6169
Before proceeding with the upgrade, you need to choose the compute tier to which you want to upgrade to perform the major version upgrade. By default, the system will upgrade from Burstable SKU to the most basic General Purpose SKU, but you can opt to upgrade to a higher compute tier if needed.
6270

0 commit comments

Comments
 (0)