Share via

Sql Server Billing is very incorrect

Dejan Popovic 0 Reputation points
2026-06-05T21:35:58.08+00:00

I have a resource group with a SQL Server and a SQL Server Database.

For my SQL Server Database, I have selected general purpose (most budget friendly), serverless, 1 max vcore 8GB allocated space. Under compute + storage it has an estimated storage cost / month as 1.6USD / month and Compute cost / vCore second = 0.000194 USD. However the estimated forecast cost for 1 month is 191.7USD.

Surely that is incorrect?

Regards,

Dean

Azure SQL Database
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 134.4K Reputation points MVP Volunteer Moderator
    2026-06-05T21:47:25.9266667+00:00

    Forecasts for Serverless are inherently inaccurate, because it all depends on how you use the service. First you need to understand that when Serverless is paused it is rolled out and exists only disk, and in this state you pay only for storage. Once someone connects to it, it is rolled in and mounted on a server, and now you start to pay for compute.

    Serverless is great for a database that you only use occasionally, like an hour a day and it is rolled out most of the day. It's a really bad option for a database that is always active, because the price for compute is higher for a provisioned general-purpose database. One risk with serverless is that you think you are not using it, but there is something that pings it every five minutes which prevents it from being paused. Keep in mind, it is the fact that it is mounted you pay for, not the actual CPU time you consume.

    If you want something which is really budget-friendly, I recommend an S0 or S1 (i.e. a DTU-based model). They are really cheap. And, no, they are overly powerful, but if you are only learning and playing, they can still serve you well.

    But going back to Serverless, it can be a great choice, if you understand the service. If you don't, it will be expensive.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-05T21:36:14.38+00:00

    The forecast isn't necessarily incorrect. The key is that Azure Cost Management shows total expected monthly cost, not just the simple “rate × 1 vCore” number shown in the SQL blade.

    Important points based on the provided context:

    1. Compute is billed per second of actual usage for serverless-style offerings, but the effective cost depends on:
      • vCore usage over time
      • Memory usage over time
      • Minimum memory allocation while the database is online
      • How long the database stays online before going idle and releasing compute
      For example, in a similar capacity-based model, compute cost is the sum of CPU and memory usage over time, and the database can stay online (and billed) for some minutes after activity stops, even if the workload only ran briefly. Only storage is billed continuously.
    2. Forecasts in Cost Management are based on historical usage, not just the configuration:
      • Cost Analysis (Resources view) groups SQL databases under their parent server and shows all charges contributing to the total.
      • If there has been recent heavy usage (for example, sustained vCore and memory consumption), Cost Management extrapolates that pattern forward for the month, which can produce a much higher forecast than the “per vCore-second” rate suggests.
    3. Storage and backup storage can add to the bill:
      • Data storage is billed based on the maximum configured size.
      • Backup storage is free up to 100% of the provisioned database size; any backup storage above that is billed separately.
      • These components are included in the monthly forecast.
    4. How to validate what is driving the 191.7 USD forecast:
      • In Cost Management → Cost Analysis, switch to the Resources view and locate the SQL server and its child database. This view groups related resources and shows the total cost per server, including database-level charges.
      • Check which meters (compute vs storage vs other add-ons) are contributing most to the current month’s cost and forecast.

    If the forecast still appears inconsistent with actual usage after checking the resource-level breakdown, open a Cost Management support request so that billing support can review the specific subscription and meters.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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