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.
Flexible Server provides maximum control for your database with a simplified developer experience and is best for workloads that require:
- Custom maintenance windows and additional configuration parameters for database optimization
- Zone-redundant and same-zone high availability with up to 99.99% SLA
- Stop/Start capabilities and burstable SKUs for cost optimization
- Hybrid Data Synchronization with data-in replication
- Offline and online migration support
Workloads with flexible compute requirements.
Burstable Compute
Instance | vCores | Memory | Pay as you go |
---|---|---|---|
Basic | 1 | 1 GB | ¥ 0.0723/hour |
B1MS | 1 | 2 GB | ¥ 0.1449/hour |
B2S | 2 | 4 GB | ¥ 0.5796/hour |
Storage
You are charged for the storage that you provision for your server. Storage can be provisioned up to 16 TB and includes 3 IOPS/GB of storage
Price | |
---|---|
GB/month | ¥ 0.8100 |
Price | |
---|---|
GB/month | ¥ 0.7653 |
Additional IOPS
You can scale your IOPS to optimize the performance of an IO intensive operation. You will be charged ¥0.3528 per IOPS per month above the included IOPS of 3 IOPS/GB. Additional IOPS are billed per minute and rounded up to the nearest minute. See more information on additional IOPS.
Price | |
---|---|
IOPS/month | ¥ 0.3528 |
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 | Note | |
---|---|---|
GB/month | ¥ 0.5472 | GRS requires twice the amount of storage capacity because it creates a replica. If you have configured the backup storage to be geo-redundant (GRS), the price will be 2x this price. Price per GB remains the same. |
Paid IO
Azure Database for MySQL will automatically scale your IOPS depending on the workload without the need for you to manually preprovision IOPS. This is a cost-effective IO model which charges only for what the workload consumes.
Price | |
---|---|
Paid IO Locally redundant storage (LRS) | ¥2 per million IOPS |
Paid IO Zone redundant storage (ZRS) | ¥2.5 per million IOPS |
Price | |
---|---|
Paid IO Locally redundant storage (LRS) | ¥0.35 per million IOPS |
Paid IO Zone redundant storage (ZRS) | ¥2.5 per million IOPS |
Most business workloads requiring balanced compute and memory with scalable I/O throughput.
Ddsv4 Series
Instance | vCores | Memory | Pay as you go |
---|---|---|---|
D2ds v4 | 2 | 8 GB | ¥ 1.1220/hour |
D4ds v4 | 4 | 16 GB | ¥ 2.2380/hour |
D8ds v4 | 8 | 32 GB | ¥ 4.4820/hour |
D16ds v4 | 16 | 64 GB | ¥ 8.9640/hour |
D32ds v4 | 32 | 128 GB | ¥ 17.9220/hour |
D48ds v4 | 48 | 192 GB | ¥ 26.8860/hour |
D64ds v4 | 64 | 256 GB | ¥ 35.8440/hour |
Instance | vCores | Memory | Pay as you go |
---|---|---|---|
D2ds v4 | 2 | 8 GB | ¥ 1.06/hour |
D4ds v4 | 4 | 16 GB | ¥ 2.21/hour |
D8ds v4 | 8 | 32 GB | ¥ 4.23/hour |
D16ds v4 | 16 | 64 GB | ¥ 8.47/hour |
D32ds v4 | 32 | 128 GB | ¥ 16.96/hour |
D48ds v4 | 48 | 192 GB | ¥ 39.94/hour |
D64ds v4 | 64 | 256 GB | ¥ 53.12/hour |
Storage
You are charged for the storage that you provision for your server. Storage can be provisioned up to 16 TB and includes 3 IOPS/GB of storage
Price | |
---|---|
GB/month | ¥ 0.8100 |
Price | |
---|---|
GB/month | ¥ 0.7653 |
Additional IOPS
You can scale your IOPS to optimize the performance of an IO intensive operation. You will be charged ¥0.3528 per IOPS per month above the included IOPS of 3 IOPS/GB. Additional IOPS are billed per minute and rounded up to the nearest minute. See more information on additional IOPS.
Price | |
---|---|
IOPS/month | ¥ 0.3528 |
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 | Note | |
---|---|---|
GB/month | ¥ 0.5472 | GRS requires twice the amount of storage capacity because it creates a replica. If you have configured the backup storage to be geo-redundant (GRS), the price will be 2x this price. Price per GB remains the same. |
Read Replica
Read replicas allow read-heavy workloads to scale out beyond the capacity of a single Azure Database for MySQL Flexible server. Each read replica is billed for provisioned compute in vCores and storage in GB/month.
High performance database workloads requiring in-memory performance for faster transaction processing and higher concurrency.
Edsv4 Series
Instance | vCores | Memory | Pay as you go |
---|---|---|---|
E2ds v4 | 2 | 16 GB | ¥ 1.7580/hour |
E4ds v4 | 4 | 32 GB | ¥ 3.5160/hour |
E8ds v4 | 8 | 64 GB | ¥ 7.0320/hour |
E16ds v4 | 16 | 128 GB | ¥ 14.0580/hour |
E32ds v4 | 32 | 256 GB | ¥ 28.1220/hour |
E48ds v4 | 48 | 384 GB | ¥ 42.1800/hour |
E64ds v4 | 64 | 504 GB | ¥ 56.2440/hour |
Instance | vCores | Memory | Pay as you go |
---|---|---|---|
E2ds v4 | 2 | 16 GB | ¥ 1.66/hour |
E4ds v4 | 4 | 32 GB | ¥ 3.33/hour |
E8ds v4 | 8 | 64 GB | ¥ 6.66/hour |
E16ds v4 | 16 | 128 GB | ¥ 13.31/hour |
E32ds v4 | 32 | 256 GB | ¥ 26.56/hour |
E48ds v4 | 48 | 384 GB | ¥ 39.94/hour |
E64ds v4 | 64 | 504 GB | ¥ 53.12/hour |
Storage
You are charged for the storage that you provision for your server. Storage can be provisioned up to 16 TB and includes 3 IOPS/GB of storage
Price | |
---|---|
GB/month | ¥ 0.8100 |
Price | |
---|---|
GB/month | ¥ 0.7653 |
Additional IOPS
You can scale your IOPS to optimize the performance of an IO intensive operation. You will be charged ¥0.3528 per IOPS per month above the included IOPS of 3 IOPS/GB. Additional IOPS are billed per minute and rounded up to the nearest minute. See more information on additional IOPS.
Price | |
---|---|
IOPS/month | ¥ 0.3528 |
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 | Note | |
---|---|---|
GB/month | ¥ 0.5472 | GRS requires twice the amount of storage capacity because it creates a replica. If you have configured the backup storage to be geo-redundant (GRS), the price will be 2x this price. Price per GB remains the same. |
Price | Note | |
---|---|---|
GB/month | ¥ 0.5472 | GRS requires twice the amount of storage capacity because it creates a replica. If you have configured the backup storage to be geo-redundant (GRS), the price will be 2x this price. Price per GB remains the same. |
Read Replica
Read replicas allow read-heavy workloads to scale out beyond the capacity of a single Azure Database for MySQL Flexible server. Each read replica is billed for provisioned compute in vCores and storage in GB/month.
FAQ
Expand allMySQL Database on Azure Retirement Customer FAQ
We have summarized detailed FAQ for your better migration experiences from MySQL Database on Azure. Please refer to the MySQL Database on Azure migration FAQ and instructions .
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.