This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 44%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPH%3C/text%3E%3C/svg%3E)
We operate a number of serverless SQL databases on Azure. Every few months one or two of them fails to pause. I'm on top of it now but early on it could be weeks before the guy who pays the bill noticed.
Sometimes provisioning the database then switching it back to serverless helps the database pause. But recently I've had to rename two before they would pause
IP addresses are restricted, usage is controlled. Its a small group so easy to confirm its not user access doing this. The db's are small (<1gb), identical structure and rules, and many have existed for months or years before they decide to stop pausing. Twice this has happened when i've been on holiday so I know they've not been connected to via most access routes.
What I have noticed is these failures to pause often (almost always) coincide with failed Power BI Service refreshes. Could it be holding open a connection, failing to close it properly?
Is there any way to find out who / what / where is keeping my database awake to confirm /deny this theory?
An Azure relational database service.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Paul Hart,
Thank you, Earland, for engaging in this thread. You are correct.
Could you please confirm if you are still experiencing the issue? This will help us provide the appropriate guidance.
Hi Paul Hart,
We didn't hear any response from you, please do let us know if you any further assistance on this, happy to help you.
Thanks!
If a connection from somewhere is left open, but remains in active that does not prevent the database to be paused. But if the connection keep pecking with a query, it's a different matter.
Why not set up an extended-events session that captures batches submitted to the database?