Edit

How a reservation discount is applied to Azure Database for MySQL

  • Article

After you buy an Azure Database for MySQL reserved capacity, the reservation discount is automatically applied to MySQL servers that match the attributes and quantity of the reservation. A reservation covers only the compute costs of your Azure Database for MySQL. You're charged for storage and networking at the normal rates.

How reservation discount is applied

A reservation discount is use-it-or-lose-it. So, if you don't have matching resources for any hour, then you lose a reservation quantity for that hour. You can't carry forward unused reserved hours.

When you shut down a resource, the reservation discount automatically applies to another matching resource in the specified scope. If no matching resources are found in the specified scope, then the reserved hours are lost.

Stopped resources are billed and continue to use reservation hours. Deallocate or delete resources or scale-in other resources to use your available reservation hours with other workloads.

Discount applied to Azure Database for MySQL

The Azure Database for MySQL reserved capacity discount is applied to running your MySQL servers on an hourly basis. The reservation that you buy is matched to the compute usage emitted by the running Azure Database for MySQL servers. For MySQL servers that don't run the full hour, the reservation is automatically applied to other Azure Database for MySQL matching the reservation attributes. The discount can apply to Azure Database for MySQL servers that are running concurrently. If you don't have an MySQL server that runs for the full hour that matches the reservation attributes, you don't get the full benefit of the reservation discount for that hour.

The following examples show how the Azure Database for MySQL reserved capacity discount applies depending on the number of cores you bought, and when they're running.

  • Example 1: You buy an Azure Database for MySQL reserved capacity for an 8 vCore. If you are running a 16 vCore Azure Database for MySQL server that matches the rest of the attributes of the reservation, you're charged the pay-as-you-go price for 8 vCore of your MySQL server compute usage and you get the reservation discount for one hour of 8 vCore MySQL server compute usage.

For the rest of these examples, assume that the Azure Database for MySQL reserved capacity you buy is for a 16 vCore Azure Database for MySQL and the rest of the reservation attributes match the running MySQL servers.

  • Example 2: You run two Azure Database for MySQL servers with 8 vCore each for an hour. The 16 vCore reservation discount is applied to compute usage for both the 8 vCore Azure Database for MySQL server.

  • Example 3: You run one 16 vCore Azure Database for MySQL server from 1 pm to 1:30 pm. You run another 16 vCore Azure Database for MySQL server from 1:30 to 2 pm. Both are covered by the reservation discount.

  • Example 4: You run one 16 vCore Azure Database for MySQL server from 1 pm to 1:45 pm. You run another 16 vCore Azure Database for MySQL server from 1:30 to 2 pm. You're charged the pay-as-you-go price for the 15-minute overlap. The reservation discount applies to the compute usage for the rest of the time.

To understand and view the application of your Azure Reservations in billing usage reports, see Understand Azure reservation usage.

Next steps

If you have questions or need help, create a support request.