Explanation
Why the waste happens and who it affects.
Over time, if actual usage remains low, these oversized allocations generate unnecessary storage costs.
In Elastic Pools, resizing can be done through standard configuration updates. In Managed Instances, reducing storage may require a shrink operation to reclaim unused space before reallocation is permitted. Without regular review, these overprovisioned environments persist as silent cost contributors.
Billing model
The pricing dimensions that drive this cost.
- Storage is billed per GB/month based on provisioned size
- Charges apply even if actual database usage is significantly lower than the allocated storage
- Additional charges apply for backup storage, compute, and IOPS depending on SKU
How to detect
4 checks to find it in your estate.
- Review total provisioned storage versus actual used capacity for Elastic Pools and Managed Instances
- Identify instances with consistently low storage usage relative to their provisioned limit
- Confirm whether current storage needs justify the allocated capacity
- Determine whether shrink operations are necessary to reclaim space
How to fix
4 ways to remove the waste.
- Where supported, reduce provisioned storage to better align with actual usage
- For Managed Instances, safely execute `DBCC SHRINKFILE` or equivalent operations before resizing
- Incorporate storage reviews into regular database hygiene practices
- Use forecasting or growth trends to balance cost savings with future scaling needs
Documentation
Vendor references for pricing and configuration.