Azure SQL Database | Reserved Instance | Compute Payment Options

Prasenna Kannan 436 Reputation points
2020-10-19T03:42:09.087+00:00

Hello,

We are planning to purchase a reserved instance for Azure SQL Single Provisioned Database. Gen5 V2 Cores.

For one year reserved instance, there are couple of options available for the purchase, one is monthly which says ($436.31 AUD) and the other is upfront which says $2831.03 AUD upfront and then monthly cost as $206.45. I could not understand the billing model here.

If the upfront cost is $2831.03 and then adding the monthly cost (206.45 * 12) => $5308.43

If we are going for monthly, it is $5235.72

The cost for going in monthly seems to be less than the upfront.

Can someone elaborate on the compute payment options?

Thanks,
Prasenna

Azure SQL Database
0 comments No comments
{count} votes

Accepted answer
  1. Anurag Sharma 17,606 Reputation points
    2020-10-19T06:37:10.777+00:00

    Hi @Prasenna Kannan , welcome to Microsoft Q&A forum. We will be glad to assist you.

    For reserved instances for the upfront cost, storage selected was 32 GB, upfront cost was $2831.03 AUD and $206.45 AUD, so total cost comes around 5308.43 yearly.

    For reserved instances for the monthly cost with the configuration provided by you, one month of cost is $436.31 AUD excluding the storage (32 GB). If you include the storage price ($6.06 AUD), monthly cost will be $442.37 AUD(as shown in below screenshot). If we calculate the yearly cost on it, it will come around $5308.44 AUD, which is almost similar.

    33190-image.png

    You can refer more on the below link for more details:
    https://azure.microsoft.com/en-us/pricing/calculator/

    Please let us know if this helps or we can discuss more on the same.

    ----------

    If answer helps, please select 'Accept Answer' as it could help other community members looking for similar queries.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.