What’s happening to Azure Database for MySQL Single Server?
On September 16, 2024, the Azure Database for MySQL Single Server will be retired. This means anyone using this server will no longer be able to create Single Server instances using the Azure portal.
The move is to make sure that all Azure Databases for MySQL can handle the array of new features and functions required by users.
It’s also to make sure that users have the most up-to-date security for their servers – which the Single Server cannot offer. If you have issues, our Azure specialist can help.
Azure Database for MySQL Single Server timeline
- January 16, 2023 – end of ability to create new Single Server instances.
- Until September 16, 2024 – you can still create read replicas from Replication blade, and use Terraform templates to create single server instances.
- September 16, 2024 – Official sunset date.
- After September 16, 2024 – no support offered for Single Server, no ability to create new instances, and no new updates released.
Migrating from Azure Database for MySQL Single Server to Flexible Server
Microsoft is recommending that those users of the Single Server migrate to the Flexible Server before the sunset date. Any users of the Single Server can migrate to Flexible Server for free.
Microsoft provides a number of ways to migrate both online and offline, though it’s not a simple process. Microsoft suggest performing test migrations first to make sure it all run correctly. To limit downtime, it also recommends using the online migration option.
For example, you cannot migrate from Single Server to Flexible Server if your Single Server has:
- Private Link enabled
- Cross-Region Read Replicas enabled
- Been deployed in regions where Flexible Server isn’t supported
What are the benefits of moving to Flexible Server?
- Cost-effective: Explore more ways to optimise costs
- Scalability: Improved performance for business-critical production workloads that require fast failover and high scalability
- Efficiencies: Improved uptime with the optional configurations and a one-hour time window for planned server maintenance
I-Finity’s approach to supporting your migration to Azure Database for MySQL Flexible Server:
- Our team will start with our discovery and assessment phase, to consider all critical data and assessing database sizes, server usage etc.
- Next, we plan using the outputs from our discovery phase for the mode of migration needed for each database to support size of data and any complexities or dependencies.
- Test migrations will be performed before anything is migrated for production – this is a critical process to ensure all aspects of the database migration is covered this includes application testing.
- Once testing is completed and passed QA, its time to plan for the migration of databases into production – we recommend performing this significant change outside of business hours/when there is little application in use.
- Our developers then manage the deployment to production with close monitoring in place ensuring any dependent applications are redirected to access the newly migrated database.
- Finally, we open all applications in production to validate running on the flexible server and monitor database performance.
If you need technical support with migrating to Flexible Server, I‑Finity has the expertise to successfully manage your migration path.
Please get in touch and we can have you moved over ahead of the retirement date.
