Skip to content

Commit c7fd3f6

Browse files
authored
Update how-to-upgrade.md
1 parent 17cb68c commit c7fd3f6

File tree

1 file changed

+18
-20
lines changed

1 file changed

+18
-20
lines changed

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

Lines changed: 18 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ This feature enables customers to perform in-place upgrades of their MySQL 5.7 s
3535

3636
## Perform a planned major version upgrade from MySQL 5.7 to MySQL 8.0 using the Azure portal for Burstable SKU servers
3737

38-
Performing a major version upgrade for an Azure Database for MySQL Burstable SKU compute tier requires a specialized workflow. This is because major version upgrades are resource-intensive, demanding significant CPU and memory. Burstable SKU instances may struggle under these requirements, potentially causing the upgrade process to fail. Therefore, when upgrading a Burstable SKU, the system first upgrades the compute tier to a General Purpose SKU to ensure sufficient resources are available for the upgrade.
38+
Performing a major version upgrade for an Azure Database for MySQL Burstable SKU compute tier requires a specialized workflow. This is because major version upgrades are resource-intensive, demanding significant CPU and memory. Burstable SKU instances being credit based may struggle under these requirements, potentially causing the upgrade process to fail. Therefore, when upgrading a Burstable SKU, the system first upgrades the compute tier to a General Purpose SKU to ensure sufficient resources are available for the upgrade.
3939

4040
To perform a major version upgrade for an Azure Database for MySQL Burstable SKU compute tier using the Azure portal, follow these steps:
4141

@@ -54,36 +54,34 @@ To perform a major version upgrade for an Azure Database for MySQL Burstable SKU
5454

5555
3. Schema Compatibility Validation
5656

57-
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.
57+
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

5959
4. Pre-Upgrade Decision
6060

61-
Before proceeding with the upgrade, you need to:
61+
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.
6262

63-
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.
64-
Automatic Compute Tier Upgrade
65-
>[!NOTE]
66-
>While your server operates in the "General Purpose" tier during the upgrade, you will only be charged for the actual "General Purpose" resources used during this period.
63+
>[!NOTE]
64+
>While your server operates in the "General Purpose" tier during the upgrade, you will only be charged for the actual "General Purpose" resources used during this period.
6765
68-
5. Post-Upgrade Decision
66+
6. Post-Upgrade Decision
6967

70-
Decide whether to retain the General Purpose SKU or revert to Burstable SKU after the upgrade. This choice will be prompted during the initial upgrade steps.
68+
Decide whether to retain the General Purpose SKU or revert to Burstable SKU after the upgrade. This choice will be prompted during the initial upgrade steps.
7169

72-
The system will automatically upgrade your compute tier from Burstable SKU to the selected General Purpose SKU support the major version upgrade.
70+
The system will automatically upgrade your compute tier from Burstable SKU to the selected General Purpose SKU support the major version upgrade.
7371

74-
5. Major Version Upgrade
72+
7. Major Version Upgrade
7573

76-
Once the compute tier is upgraded, the system will initiate the major version upgrade process. Monitor the upgrade progress through the Azure portal. The upgrade process might take some time depending on the size and activity of your database.
77-
78-
>[!Note]
79-
>If the major version upgrade fails, the compute tier will not automatically revert to the previous Burstable SKU. This is to allow customers to continue the major version upgrade without needing to perform the compute tier upgrade again.
80-
81-
6. Automatic Reversion
74+
Once the compute tier is upgraded, the system will initiate the major version upgrade process. Monitor the upgrade progress through the Azure portal. The upgrade process might take some time depending on the size and activity of your database.
75+
76+
>[!Note]
77+
>If the major version upgrade fails, the compute tier will not automatically revert to the previous Burstable SKU. This is to allow customers to continue the major version upgrade without needing to perform the compute tier upgrade again.
8278
83-
Based on your pre-upgrade decision, the system will either retain the General Purpose SKU or automatically revert to Burstable SKU after the upgrade is complete.
79+
8. Automatic Reversion
8480

85-
>[!Note]
86-
>If you chose to automatically revert to Burstable SKU, the system will revert to the B2S SKU by default.
81+
Based on your pre-upgrade decision, the system will either retain the General Purpose SKU or automatically revert to Burstable SKU after the upgrade is complete.
82+
83+
>[!Note]
84+
>If you chose to automatically revert to Burstable SKU, the system will revert to the B2S SKU by default.
8785
8886
## Perform a planned major version upgrade from MySQL 5.7 to MySQL 8.0 using the Azure portal for none Burstable SKU servers
8987

0 commit comments

Comments
 (0)