Thank you all for an overwhelming response to our Flexible Server release! Your continued feedback is critical to ensure that we invest in the features that are most important for you. Today, I am excited to share some exciting new features that we released last week, driven by your feedback.
With MySQL v8.0, the MySQL Server Team continues to add exciting new features in every minor version release, and it's sometimes difficult to keep up (which is a good problem to have :smiling_face_with_smiling_eyes:). Immediately after Flexible Server release, many of you requested that we prioritize MySQL 8.0 ASAP to unblock your to move Flexible Server, and some of you were looking for MySQL 8.0.20 or later to leverage some exciting improvements from the community. Today, we're happy to share that MySQL 8.0.21 is now available in Flexible Server in all major Azure regions. You can use the Azure portal, the Azure CLI, or Azure Resource Manager templates to provision the MySQL 8.0.21 release as shown below.
az mysql flexible-server create --resource-group <resourcegroupname> --name <servername> --location <region> --admin-user <username> --admin-password <password> --sku-name Standard_B1ms --version 8.0.21 --public-access <your Client IP address>
One of the highlights of Flexible Server architecture is zone awareness and the ability for you to configure zone redundant high availability. But many of you asked for the flexibility to choose availability zones at server creation, similar to Azure VMs, VM Scale Sets, or Azure Kubernetes Services, which would allow you to collocate your application and database in the same Availability zones to minimize database latency and improve performance. Well, Flexible Server is all about the flexibility and controls that you are looking for. You can now specify your preferred Availability zone at the time of server creation as shown below.
Note: Not all Azure regions support availability zones today, so if you select a region that doesn't yet support multiple availability zones, you might not see this this functionality. You can find Azure regions that support availability zone here and the regions that support Flexible servers here.
When you provision an Azure Database for MySQL server (Single Server or Flexible Server), you get 3 IOPs per GB free for you to consume. When you want to perform migrations or data load operations, the complimentary IOPs can be too small, which can result in significant performance degradation, yet you don’t want to increase storage size as your IOPs scaling requirements are transient. Your feedback strongly indicated that you wanted us to provide the flexibility to scale up or down the IOPs provisioned for the server independently of the storage, which would enable you to scale up IOPs to perform transient operations such as migrations or data loads more quickly. We've now decoupled storage and IOPs, and you can provision additional IOPs beyond the complimentary IOPs (3 IOPs per GB) for operations such as migrations and data loads, and then scale it back down when not required to save cost. In addition, further IOPs scaling is a fully online operation that doesn't require any downtime or restarts. The maximum IOPs you can provision is limited by the Compute VM size you choose. For more details, refer to our documentation.
As you get ready to test Flexible Server, it's important to call out some of the known issues we are working on as this blog is written.
We hope you are enjoying the new Flexible Server experience with our Azure Database for MySQL service. If you have any issues, feedback, or requests, please reach out to us using the following channels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.