Azure SQL database charges keep climbing while db is paused

Question

Hello,

I've observed that my Azure SQL database continues to accrue charges even when it is in a paused state. To clarify the current setup:

The only service that connects to the database is an App Service hosting a Web API, which is currently disabled.

SQL Server networking is restricted to only three IP addresses my personal IP and the two outbound IPs associated with the App Service.

Occasionally, I connect to the database using SSMS, but I always ensure that connections are closed and that no transactions remain open.

I’ve also run various diagnostic scripts, some provided by ChatGPT, to check for active sessions or connections, and none were found.

From documentation and guidance, I understand that the database should not incur compute charges when it is paused, provided there are no active connections.

Given all of this, I'm trying to understand why charges are still accumulating even after the database has paused.

Could you help clarify what might be keeping the database "warm" or triggering compute costs in this state?

Answer 1

Hi Jason Halvorson,

Greetings!!

When Azure SQL Database serverless is paused there is no cost for Compute, however, you still have to pay for storage. For more information, please refer the document: https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview?view=azuresql&tabs=general-purpose#cost

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.