azure-deprecation / dashboard

Notices about Azure services & features being deprecated
https://azure-deprecation-notices.cloud
MIT License
135 stars 6 forks source link

Azure Database for MySQL Single Server is retiring on September 16th, 2024 #279

Open azure-deprecation-automation opened 1 year ago

azure-deprecation-automation commented 1 year ago

Azure Database for MySQL Single Server is retiring on September 16th, 2024

Deprecation ID: 2bc79150-9251-4c81-b344-abd4a9c2e61d Deadline: Sep 16, 2024 Impacted Services:

More information:

Notice

Here's the official report from Microsoft:

On 16 September 2024, Azure Database for MySQL Single Server will be retired, and you'll need to migrate to Flexible Server by that date.

Flexible Server is a new, fully managed, production-ready database service that offers multiple improvements over Single Server, including:

  • More ways to optimize costs, including support for burstable tier compute options.
  • Improved performance for business-critical production workloads that require low latency, high concurrency, fast failover, and high scalability.
  • Improved uptime with the ability to configure a hot standby on the same or a different zone, and a one-hour time window for planned server maintenance.

Timeline

Phase Date Description
Announcement Sep 30, 2022 Deprecation was announced
Deprecation Sep 16, 2024 Offering will no longer be available.

Impact

Azure Database for MySQL Single Server is retiring on September 16th, 2024 and migration to Azure Database for MySQL Flexible Server is required.

Required Action

A migration FAQ is provided here and you can migrate to flexible server with Azure Data Migration Service.

Here's the official report from Microsoft:

Use Azure Data Migration Service to migrate to Azure Database for MySQL Flexible Server by 16 September 2024 (read the FAQ to learn more).

Contact

You can get in touch through the following options:

azure-deprecation-automation commented 1 year ago

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.