Azure SQL Right-sizing
The database is billed for the vCores it is provisioned with, not the vCores it uses, so headroom nobody consumes is billed at the same rate as work.
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: Rightsize the SQL database. 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.
- Confirm the recommendation tier against Query Performance Insight P95 DTU/CPU before applying.
- Pick the next smaller tier in the same purchasing model (DTU or vCore); review the storage cap to ensure your database fits.
- Save. Monitor DTU/CPU for a week and roll forward if utilisation stays under target.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-230- Full reference
Related checks
See the oversized 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.