Skip to content

Commit 81a4905

Browse files
committed
corr3
1 parent 8ff0b27 commit 81a4905

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/mysql/single-server/whats-happening-to-mysql-single-server.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,8 +88,8 @@ After the forced migration, you must reconfigure the features listed above on th
8888
> [!NOTE]
8989
> If your server is in a region where Azure Database for MySQL - Flexible Server is not supported, then post the sunset date, your Single Server instance will be available with limited operations to access data and to be able to migrate to Flexible Server. Your instance will not be force-migrated to Flexible Server. We strongly recommend that you use one of the following options to migrate before the sunset date to avoid any disruptions in business continuity:
9090
>
91-
> 1.Use Azure DMS to perform a cross-region migration to Flexible Server in a suitable Azure region.
92-
> 2.Migrate to MySQL Server hosted on a VM in the region, if you are unable to change regions due to compliance issues.
91+
> - Use Azure DMS to perform a cross-region migration to Flexible Server in a suitable Azure region.
92+
> - Migrate to MySQL Server hosted on a VM in the region, if you are unable to change regions due to compliance issues.
9393
9494
## Frequently Asked Questions (FAQs)
9595

0 commit comments

Comments
 (0)