Azure SQL Multiple Small DBs Could Use Elastic Pool
An elastic pool buys one shared allocation for many databases with staggered peaks, instead of provisioning each one for its own peak separately.
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 into an elastic pool. 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
- Identify other small databases on the same server with similar peak windows.
- Open Portal → SQL servers → ‹server› → Elastic pools → Create elastic pool.
- Add the resource plus the sibling databases, set the pool eDTU to cover combined peak load.
- Configure per-database min/max DTU caps to prevent a noisy neighbour starving the pool.
- Watch Query Performance Insight for the first week and tune.
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-1334
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.