I am trying to understand why my Azure SQL Database will not autopause.
When I look at the "compute utilization" graph showing CPU, Data IO and Log IO percentages, they are flat while the "App CPU billed" chart shows vcore seconds being billed and the status shows "online".
Digging deeper I added some metrics to the compute utilization graph: Failed connections, successful connections and sessions percentage. I found that some services were connecting to the database from the only vm that knows anything about the db, so I reconfigured them to shut off until morning.
All during the night I continued to get "App CPU billed" with the DB online even though the CPU, Data IO, Log IO, Failed connections, Successful connections and sessions percentage were all at zero. No auto pause.
The only way I can get the DB to auto pause is to turn off the VM or the two services that connect to the databases on that VM, but as I stated above there are no connections showing for the entire evening so I am at a loss as to what is keeping the DB from auto pausing.
According to docs:
Autopausing is triggered if all of the following conditions are true for the duration of the autopause delay:
Number sessions = 0
CPU = 0 for user workload running in the user pool
How can I determine why the DB is not auto pausing? What additional metrics can I track to know what activity is triggering activity on the DB?
