Azure SQL Reserved Capacity
The database runs continuously at a fixed vCore count, which is the usage shape reserved capacity is priced for.
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: Buy a reservation for 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 → Reservations → Add → SQL Database.
- Choose the region, performance tier, and term that match this database's expected utilisation.
- Pick scope: single-subscription if only this account uses the tier, shared if other subscriptions can borrow it.
- Review and Buy. Track utilisation in Cost Management → Reservations → Utilisation.
These are the steps the finding carries in the product.
- Category
- Commitment discounts. Reserved Instance, Savings Plan and Committed Use opportunities, where steady usage justifies a commitment.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-231- Full reference
Related checks
See the discount opportunities 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.