Azure SQL Could Use Serverless Tier
A provisioned database is billed for its vCores continuously; serverless bills for the seconds it is actually active and pauses when it is not.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
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: Move the SQL database to the serverless tier. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- SQL Databases on Azure
- The fix, by hand
- Open Portal → SQL databases → the resource → Compute + storage.
- Switch the Compute tier from Provisioned to Serverless. Pick min/max vCores that bracket your observed CPU range.
- Set Auto-pause delay (≥60 minutes). Confirm clients have retry logic that tolerates the cold-start.
- Apply. Monitor Query Performance Insight for cold-start latency over the next week.
These are the steps the finding carries in the product.
- Category
- Scheduling. Resources running 24x7 with a clear off-hours usage pattern, ready for start and stop scheduling.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1335- Full reference
Related checks
See the always-on 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.