Azure Synapse SQL Pool Idle
A dedicated SQL pool bills for its provisioned DWU level until it is paused; idleness alone does not pause it.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Pause the idle Synapse SQL pool. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight pauses the service, then checks the change took.
- Applies to
- Synapse SQL Pools on Azure
- The fix, by hand
- Review Synapse SQL pool utilisation in Azure Portal.
- Pause the idle SQL pool to stop DWU billing.
- Scale down DWU before pausing if a fast resume is expected.
- Consider auto-pause settings for development pools.
ZopNight does this for you after a guided review.
- Category
- Idle resources. Resources running but doing no useful work: zero invocations, no connections, no traffic.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-260
Related checks
See the idle resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.