Azure Database for MySQL delivers fully trusted, enterprise-ready Community MySQL database as a service. The MySQL Community edition helps you easily move to the cloud using languages and frameworks of your choice. Most importantly, you will get built-in high availability and dynamic scaling to help you easily adapt to changes in customer demands. In addition, you can benefit from unrivaled security and compliance, including Azure IP advantage and Azure’s industry leading business coverage. All these with a flexible pricing model so that you can choose the resources for your workload without any hidden cost.
Community MySQL that’s fully trusted
Combine MySQL Community edition with the advantages of being a fully trusted service provider in order for developers to easily manage infrastructure and database, allowing them to focus on building exceptional applications.
Languages and frameworks of your choice
Azure Database for MySQL supports popular open source frameworks and languages, offering tight integration with Azure Web applications. Popular content management applications (such as WordPress and Drupal) deliver a fully integrated experience supporting your application development demands.
Built-in high availability
Trust Azure to keep your enterprise applications running continuously. Azure Database for MySQL offers high availability (99.99% SLA) to ensure your applications run as per normal when needed without extra configuration, replication or cost.
Scale within seconds
Provision within minutes and scale compute or storage with independence and flexibility within seconds.
Simple and flexible pricing
Enjoy everything you need with simple and flexible pricing. Azure Database for MySQL delivers all capabilities you need, including capabilities such as automatic database patching, automatic backup, built-in monitoring, security, and more, at no extra cost.
Unrivaled security and coverage
Run your app on top infrastructure and the world’s most trusted cloud. Azure Database for MySQL is a fully integrated service that offers you Microsoft global network of datacenters, unrivaled security and round-the-clock monitoring.
What can you build with Azure Database for MySQL?
Use the state-of-the-art machine learning algorithms and integrated visualization tools to develop complex and transformational applications to obtain actionable insights and analysis.
Retail and e-commerce
Build secure, scalable e-commerce solutions that meet the demands of both customers and businesses. Engage customers with customized products and offers, process transactions quickly and securely and focus on product delivery and customer service.
Scalable Web and mobile applications
Swiftly build engaging and scalable cross-platform and native applications for iOS, Android, Windows or Mac.
Engage customers around the world with a rich and personalized digital marketing experience. Quickly build and launch automatically scalable digital marketing campaigns based on customer demands.
Finance management applications
Securely store critical data and deliver high-value analytics and insights over aggregated data to users, using in-built security and performance.
Flexibly scale databases to accommodate unpredictable bursts of traffic and deliver low latency multi-player experiences.
MySQL Database on Azure Retirement Customer FAQ
We are ending the MySQL Database on Azure service on Dec 1st, 2019, which will be replaced by the Azure Database for MySQL service.
If you are an existing customer:
- · No interruption of service
- · You will be automatically migrated to the new service before the end of life of the existing service
- · Migration will begin on Feb 15th, 2019
- · Special pricing will be lost when scaled to a different service tier or if server is deleted
- · You will continue to pay the same price post migration. Detailed information about the SKU mapping between the old service and the new service will be published before end of December 2018
- · No action necessary for now. At a minimum, 30 days prior to your scheduled migration you will receive additional notifications including the exact timeline for your migration
If you are a new customer:
- · You will not be accepted on the “MySQL Database on Azure” service as of the date of this announcement
Will my total bill increase when moving from MySQL Database on Azure to Azure Database for MySQL?
No. Your monthly total bill once on Azure Database for MySQL will be the same as your total monthly bill on MySQL Database on Azure. For example: if you are an MS4 customer currently paying ¥1,071.36 per month for MySQL Database on Azure, you will continue to pay ¥1,071.36 per month once on Azure Database for MySQL.
Will my bill look different after I migrate from MySQL Database on Azure to Azure Database for MySQL? How will my bill look different?
Yes, your bill will look different after we migrated you from MySQL Database on Azure to Azure Database for MySQL, but your total bill amount will remain the same. Today with MySQL Database on Azure you are charged for the version you are using (MS1, MS2, MS3, MS4, MS5, MS6, MP1, or MP2), which includes a free amount of storage called “free database capacity”. If you use more storage than is included in this free database capacity, then you are billed ¥0.6116 per GB per month for that excess storage.
After the migration to Azure Database for MySQL, you will be charged for the compute and storage resources you provision. Compute resources are charged per vCore per hour. Storage is charged per provisioned GB per month. Azure Database for MySQL does not include “free database capacity”.
Let us look at an example that describes how you will be billed before and after you migrate to Azure Database for MySQL:
Let us assume you are using MS5 with 200 GB of storage. MS5 includes 100 GB of “free database capacity”. That makes the bill look like this:
- MS5 server: ¥2.1613 per hour x 744 hours per month = ¥1,608.01 per month
- Storage Overage: ¥0.6116 per GB per month x (200 GB used – 100 GB free) = ¥61.16 per month
- Total Bill: ¥1,608.01 per month + ¥61.16 per month = $1,669.17 per month
During the migration to Azure Database for MySQL the MS5 server will migrate to General Purpose 4 vCore with 200 GB provisioned storage. The pricing look as follows:
- Compute: ¥0.5198 per vCore per hour x 4 vCore x 744 hours per month = ¥1,546.85 per month
- Storage: ¥0.6116 per GB per Month x 200 GB = ¥122.32 per month
- Total Bill: ¥1,546.85 per month + ¥122.32 per month = $1,669.17 per month
So in this example, the total monthly bill for MySQL Database on Azure MS5 and the equivalent offer on Azure Database for MySQL is the same.
How will you maintain my total bill if you are charging for storage?
MySQL Database on Azure includes a free amount of storage called “free database capacity”. This free database capacity varies by version (MS1, MS2, MS3, MS4, MS5, MS6, MP1, or MP2).
Azure Database for MySQL does not include free storage. Instead Azure Database for MySQL charges for compute in vCores per hour and provisioned storage in GB per month separately. Each MySQL Database on Azure migrated to Azure Database for MySQL will be provisioned with a minimum storage size equivalent to the free database capacity for MySQL Database on Azure. For example, if you are an MS1 customer, your database will be provisioned with a minimum of 100 GB of storage.
To maintain the same total monthly bill for customers who have migrated from MySQL Database on Azure to Azure Database for MySQL, migrated customers will be billed using a special “legacy” compute and storage meters that maintain your total monthly bill. These “legacy” meters are priced to offset the loss of the “free database capacity” included in MySQL Database on Azure.
What happens if I notice an increase in my total bill?
You should not see an increase in your total monthly bill. If you do, please open a support ticket so that the team can investigate.
How will my server be mapped to the new offering?
We will publish detailed mapping information before end of December 2018.
When will my server be migrated?
You will get an email notification at least 30 days prior to the date your server is scheduled to migrate. Migrations will not start before Feb 15th, 2019.
How will the billing meters be mapped?
We will publish detailed meter mapping information before end of December 2018.
Do I have to migrate myself or will you provide assistance to migrate?
You do not have to take any action, your MySQL server will be migrated for you. You will receive another communication with additional details 30 days prior to your scheduled migration. Please file a support ticket if you wish to be migrated earlier.
What if I migrate to using a mysqldump and mysqlrestore?
You can migrate using mysqldump and mysqlrestore, however you will not be able to maintain use the “legacy” meters put in place to maintain your exact current price points. You will be billed using new pricing model.
What happens if I want to change the performance level after I migrate (ex: I have migrated to a General Purpose 4 vCore from MS5, and then want to upgrade to General Purpose 8 vCore)?
If you decide to increase your database size once on Azure Database for MySQL after you have migrated, you will no longer receive the “legacy” prices, but will migrate to the Azure Database for MySQL prices as displayed here.
What is the experience during the migration?
The impact to your server and workload will be minimal. We migrate server from MySQL Database for Azure to the new Azure Database for MySQL using replication. This means that the server will be online during the migration except for the final phase of the migration that includes the failover to the new server. The connection string to the server will remain the same, so that you do not have to change your application logic. Below are the migration steps in short:
- We take a snapshot of the server in MySQL Database for Azure.
- We restore that snapshot in a new Azure Database for MySQL server.
- Set up replication between the old and the new server to catch up all changes since the snapshot.
- When the new server is caught up except for in-flight transactions, we set the old server to read-only mode for new transactions.
- The new server catches up with the latest changes and we stop the replication.
- We then copy configurations, firewall rules and redirect DNS from the old to the new server and finally stop the old server.
- All new connections to against the new server. No changes to your application are required.