Header Place holder

Azure Database for MySQL

Managed MySQL database service for app developers

1RMB Trial Buy Now

We are ending the MySQL Database on Azure service on December 1st, 2019, which will be replaced by the Azure Database for MySQL service. Please scroll down to FAQ below.

Azure Database for MySQL provides a fully managed database service for app development and deployment with built-in capabilities, such as high availability, at no extra cost.

Workloads requiring light compute and I/O performance.

Compute

Compute is provisioned in virtual cores (vCores). A vCore represents a logical CPU offered with an option to choose between compute generations.

Compute Gen 4

Gen 4 logical CPUs are based on Intel E5-2673 v3 (Haswell) 2.4 GHz processors.

vCore Price
1 ¥0.2699/hour
(~¥200.8056/month)
2 ¥0.5398/hour
(~¥401.6112/month)

Compute Gen 5

Gen 5 logical CPUs are based on Intel E5-2673 v4 (Broadwell) 2.3 GHz processors.

vCore Price
1 ¥0.2699/hour
(~¥200.8056/month)
2 ¥0.5398/hour
(~¥401.6112/month)

Storage

You are charged for the storage that you provision for your server. Storage can be provisioned up to 1 TB.

Price
GB/month ¥0.7938

Backup

Backup storage is the storage associated with automated backups of your server. Increasing your backup retention period increases the backup storage that is consumed by your server. There is no additional charge for backup storage for up to 100% of your total provisioned server storage. Additional consumption of backup storage will be charged in GB/month.

Price
Locally redundant GB/month ¥0.7938

I/O

Price
IM Operations ¥0.7938

Most business workloads requiring balanced compute and memory with scalable I/O throughput.

Compute

Compute is provisioned in virtual cores (vCores). A vCore represents a logical CPU offered with an option to choose between compute generations.

Compute Gen 4

Gen 4 logical CPUs are based on Intel E5-2673 v3 (Haswell) 2.4 GHz processors.

vCore Price
2 ¥0.6676/hour
(~¥496.6944/month)
4 ¥1.3352/hour
(~¥993.3888/month)
8 ¥2.6704/hour
(~¥1,986.7776/month)
16 ¥5.3408/hour
(~¥3,973.5552/month)
32 ¥10.6816/hour
(~¥7,947.1104/month)

Compute Gen 5

Gen 5 logical CPUs are based on Intel E5-2673 v4 (Broadwell) 2.3 GHz processors.

vCore Price
2 ¥0.6676/hour
(~¥496.6944/month)
4 ¥1.3352/hour
(~¥993.3888/month)
8 ¥2.6704/hour
(~¥1,986.7776/month)
16 ¥5.3408/hour
(~¥3,973.5552/month)
32 ¥10.6816/hour
(~¥7,947.1104/month)

Storage

You are charged for the storage that you provision for your server. Storage can be provisioned up to 2 TB.

Price
GB/month ¥0.8033

Backup

Backup storage is the storage associated with automated backups of your server. Increasing your backup retention period increases the backup storage that is consumed by your server. There is no additional charge for backup storage for up to 100% of your total provisioned server storage. Additional consumption of backup storage will be charged in GB/month.

Price
Locally redundant GB/month ¥0.7938
Geographically redundant GB/month ¥1.5875

High performance database workloads requiring in-memory performance for faster transaction processing and higher concurrency.

Compute

Compute is provisioned in virtual cores (vCores). A vCore represents a logical CPU offered with an option to choose between compute generations.

Compute Gen 5

Gen 5 logical CPUs are based on Intel E5-2673 v4 (Broadwell) 2.3 GHz processors.

vCore Price
2 ¥1.8748/hour
(~¥1394.8512/month)
4 ¥3.7496/hour
(~¥2789.7024/month)
8 ¥7.4992/hour
(~¥5579.4048/month)
16 ¥14.9984/hour
(~¥11158.8096/month)

Storage

You are charged for the storage that you provision for your server. Storage can be provisioned up to 2 TB.

Price
GB/month ¥0.8033

Backup

Backup storage is the storage associated with automated backups of your server. Increasing your backup retention period increases the backup storage that is consumed by your server. There is no additional charge for backup storage for up to 100% of your total provisioned server storage. Additional consumption of backup storage will be charged in GB/month.

Price
Locally redundant GB/ ¥0.7938
Geographically redundant GB/month ¥1.5875

FAQ

Expand all

MySQL Classic Retirement Customer FAQ

We are ending the MySQL Database on Azure service on December 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 have published detailed meter mapping information here for your reference.

  • 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 have published detailed meter mapping information here for your reference.

  • 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:

    1. We take a snapshot of the server in MySQL Database for Azure.
    2. We restore that snapshot in a new Azure Database for MySQL server.
    3. Set up replication between the old and the new server to catch up all changes since the snapshot.
    4. When the new server is caught up except for in-flight transactions, we set the old server to read-only mode for new transactions.
    5. The new server catches up with the latest changes and we stop the replication.
    6. We then copy configurations, firewall rules and redirect DNS from the old to the new server and finally stop the old server.
    7. All new connections to against the new server. No changes to your application are required.

General

  • What are the differences between the Basic, General Purpose, and Memory Optimized tiers?

    The Basic tier is designed for workloads requiring light compute and I/O performance. Examples include servers used for development or testing, or small-scale infrequently used applications. General Purpose is for most business workloads requiring balanced compute and memory with scalable I/O throughput. Examples include servers for hosting Web and Mobile apps, and other enterprise applications. The Memory Optimized tier is for high performance database workloads requiring in-memory performance for faster transaction processing and higher concurrency. Examples include servers for processing real-time data and high performance transactional or analytical apps. Please review the documentation for more details.

  • How is my bill calculated

    For all tiers, the service is billed on a predictable, hourly rate based on pricing tier, provisioned compute in vCores, and provisioned storage in GB/month for your server and backups. On your bill, vCore hours, storage GB/month for the server and storage GB/month for backups will have separate line items.

  • What if a single MySQL server is active for less than an hour or uses a higher pricing tier for less than an hour?

    You are billed for each hour or portion thereof that a MySQL server exists, regardless of whether the server was active for the full hour. If you have scaled your database, you will be billed using the highest pricing tier, provisioned vCore and provisioned storage during the hour.

    For example:

    • If you create a MySQL server and delete it after five minutes, you are charged for one full hour for the provisioned compute and storage.
    • If you create a MySQL server in the General Purpose tier with 8 vCores and then immediately upgrade it to 16 vCores in the General Purpose tier, you are charged at the 16 vCore rate for the first hour.
  • How is the backup charge calculated?

    Backup storage is the storage associated with automated backups of your server. Increasing your backup retention period increases the backup storage that is consumed by your MySQL server. There is no additional charge for backup storage for up to 100% of your total provisioned server storage. Additional consumption of backup storage will be charged in GB/month. For example, if you have the database storage size of 100 GBs, you will get 100 GBs of backup at no additional cost. However, if the backup is 110 GBs, you will pay for the 10 GBs.

Support & SLA

If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.

MySQL Database on Azure provides a Service Level Agreement for 99.9% operating time to ensure high availability and business continuity for users. To learn more about the details of our Service Level Agreement, please visit the Service Level Agreements page.

Are you ready to start?

Apply for a 1RMB Trial, and get an ¥ 1,500 free credit limit with Azure

1RMB Trial