完全受控、可調整的 MySQL 資料庫
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.
探索定價選項
套用篩選以根據您的需求自訂定價選項。
價格僅為估算值，並非實際價格報價。實際定價可能會根據與 Microsoft 簽訂的合約類型、購買日期和目前貨幣匯率而有所不同。價格是根據美元計算，並使用前一個月底最後一個工作天之前兩個工作天內擷取的倫敦即期匯率進行轉換。如果月底的前兩個工作天是主要市場中的銀行假日，則匯率設定日期通常為兩個工作天之前的那一天。此匯率適用於下個月的所有交易。登入 Azure 定價計算機查看依據您目前 Microsoft 方案/供應項目所訂的定價。如需定價的詳細資訊或要求報價，請連絡 Azure 銷售專員。請參閱 Azure 定價常見問題集。
美國政府機構有資格透過授權解決方案提供者購買 Azure Government 服務，無須預先支付費用；亦可直接透過隨用隨付線上訂用帳戶購買。
重要 - 以 R$ 表示的價格僅供參考；這是國際交易，因此最終價格需視匯率與是否內含 IOF 稅而定，而且不會發行 eNF。
美國政府機構有資格透過授權解決方案提供者購買 Azure Government 服務，無須預先支付費用；亦可直接透過隨用隨付線上訂用帳戶購買。
重要 - 以 R$ 表示的價格僅供參考；這是國際交易，因此最終價格需視匯率與是否內含 IOF 稅而定，而且不會發行 eNF。
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
Burstable
Workloads with flexible compute requirements.
Burstable Compute
| Instance | vCores | Memory | 隨用隨付 |
|---|---|---|---|
| B1ms | 1 | 2 GiB | $- |
| B1s | 1 | 1 GiB | $- |
| B2ms | 2 | 8 GiB | $- |
| B2s | 2 | 4 GiB | $- |
| B4ms | 4 | 16 GiB | $- |
| B8ms | 8 | 32 GiB | $- |
| B12ms | 12 | 48 GiB | $- |
| B16ms | 16 | 64 GiB | $- |
| B20ms | 20 | 80 GiB | $- |
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 | $- |
Additional IOPS
You can scale your IOPS to optimize the performance of an IO-intensive operation. Additional IOPS beyond the provisioned amount will incur charges based on the usage, rounded up to the nearest minute. See more information on additional IOPS.
| Price | |
|---|---|
| IOPS/month | $- |
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. Learn more
| Price | |
|---|---|
| Paid IO Locally redundant storage (LRS) | $- per million IOPS |
| Paid IO Zone redundant storage (ZRS) | $- per million IOPS |
Backup Storage
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 | $- | 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. |
General Purpose
Most business workloads requiring balanced compute and memory with scalable I/O throughput.
General Purpose
| Instance | vCores | Memory | 隨用隨付 | 保留 1 年 | 保留 3 年 |
|---|---|---|---|---|---|
| D Series | 2 | 8 GiB | $- |
$-
|
$-
|
| D Series | 4 | 16 GiB | $- |
$-
|
$-
|
| D Series | 8 | 32 GiB | $- |
$-
|
$-
|
| D Series | 16 | 64 GiB | $- |
$-
|
$-
|
| D Series | 32 | 128 GiB | $- |
$-
|
$-
|
| D Series | 48 | 192 GiB | $- |
$-
|
$-
|
| D Series | 64 | 256 GiB | $- |
$-
|
$-
|
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.
Business Critical
High performance database workloads requiring in-memory performance for faster transaction processing and higher concurrency.
Business Critical
| Instance | vCores | Memory | 隨用隨付 | 保留 1 年 | 保留 3 年 |
|---|---|---|---|---|---|
| E Series | 2 | 16 GiB | $- |
$-
|
$-
|
| E Series | 4 | 32 GiB | $- |
$-
|
$-
|
| E Series | 8 | 64 GiB | $- |
$-
|
$-
|
| E Series | 16 | 128 GiB | $- |
$-
|
$-
|
| E Series | 32 | 256 GiB | $- |
$-
|
$-
|
| E Series | 48 | 384 GiB | $- |
$-
|
$-
|
| E Series | 64 | 504 GiB | $- |
$-
|
$-
|
| E Series | 80 | 504 GiB | $- |
$-
|
$-
|
| E Series | 96 | 672 GiB | $- |
$-
|
$-
|
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.
Azure 定價與購買選項
其他資源
適用於 MySQL 的 Azure 資料庫
深入了解 適用於 MySQL 的 Azure 資料庫 的功能。
定價計算機
預估您使用任何 Azure 產品組合的預期每月費用。
SLA
檢閱 適用於 MySQL 的 Azure 資料庫 的服務等級協定。
文件
檢閱技術教學課程、影片和更多 適用於 MySQL 的 Azure 資料庫 資源。
常見問題集
-
Flexible Server is billed on a predictable, hourly rate. You are billed for the compute and storage you provision and the backup storage you consume. On your bill, you will see a separate line item for compute, storage, and backup storage. Compute is billed per vCore-hour. Storage and backup storage are billed per GB-month.
-
For each read replica you create, you are billed for the provisioned compute in vCores and provisioned storage in GB-month in the region where your replica is provisioned.
-
Servers enabled with HA have a primary and secondary replica. Secondary replica can be in same zone or zone redundant. You are billed for the provisioned compute and storage for both the primary and secondary replica. For example, if you have a primary with 4 vCores of compute and 512 GB of provisioned storage, your secondary replica will also have 4 vCores and 512 GB of provisioned storage. Your zone redundant HA server will be billed for 8 vCores and 1,024 GB of storage. An extra 36 IOPs per node in addition to the configured IOPs on your servers will be added and reserved, so additional charges for the 72 IOPs per month would apply based on your Azure region for HA enabled servers. Depending on your backup storage volume, you may also be billed for backup storage.
-
Backup storage is the storage associated with automated backups of your server, including data and log backups. 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 storage for your primary server. Additional consumption of backup storage will be charged in GB-month. For example, if your primary server has a storage size of 512 GBs, you will get 512 GBs of backup at no additional cost. However, if the backup is 612 GBs, you will pay for the incremental 100 GBs.
-
You are billed for each full hour that your server exists regardless of whether the server was active for the full hour. If you have scaled up your database, you will be billed for the higher number of vCores used within the hour. If you have switched between two compute tiers, you will be billed for the higher priced compute tier.
For example:
- If you create a server and delete it after five minutes, you are charged for one full hour for the provisioned compute and storage.
- If you create a server with 8 vCores of General Purpose compute and then immediately scale up to 16 vCores of General Purpose compute, you are charged for 16 vCores of General Purpose compute for the first hour.
- If you create a server with General Purpose compute with 8 vCores and then immediately upgrade it to Memory Optimized compute with 8 vCores, you are charged for 8 vCores Memory Optimized compute for the first hour.
-
While your server is stopped, you will only be billed for the storage you have provisioned and any backup storage you consume that exceed 100% of your primary provisioned storage volume. While your server is stopped, you will not be billed for compute.
-
Yes. Standard networking charges apply for network egress. Refer here for more details.
與銷售專員洽談，取得 Azure 定價的逐步解說。了解您雲端解決方案的定價。
取得免費的雲端服務，以及可於 30 天內用來探索 Azure 的 $200 點數。