# Overprovisioned compute tier in Azure SQL Database Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-compute-tier-in-azure-sql-database Azure SQL Database resources are frequently overprovisioned due to default configurations, conservative sizing, or legacy requirements that no longer... By: Balazs Engedi Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Overprovisioned Compute Tier in Azure SQL Database The short version Azure SQL Database resources are frequently overprovisioned due to default configurations, conservative sizing, or legacy requirements that no longer apply. [Balazs Engedi](https://www.linkedin.com/in/engedib/) FinOps Specialist @ KPN Azure service [Azure SQL](https://www.pointfive.co/efficiency-hub/cloud-services/azure-sql) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0028 Type Overprovisioned Resource ## Explanation Why the waste happens and who it affects. This inefficiency appears across all deployment models: - Single Databases may be assigned more DTUs or vCores than the workload requires - Elastic Pools may be oversized for the actual demand of pooled databases - Managed Instances are often deployed with excess compute capacity that remains underutilized Because billing is based on provisioned capacity, not actual consumption, organizations incur unnecessary costs when sizing is not aligned with workload behavior. Without regular reviews, these resources become persistent sources of waste - especially across dev/test environments or variable workloads. ## Billing model The pricing dimensions that drive this cost. - Billed based on provisioned compute resources (DTUs or vCores), regardless of usage (provisioned compute tier) - Storage billed per GB/month - Higher tiers (e.g., Business Critical, Premium) incur significantly greater cost - For provisioned compute, charges apply whether the database is actively used or idle (the serverless tier bills compute per second of use and bills only storage while auto-paused) ## How to detect 4 checks to find it in your estate. - Identify SQL Databases, Elastic Pools, or Managed Instances with consistently low CPU and memory utilization - Review actual workload patterns and performance requirements relative to the provisioned tier - Determine whether the workload could perform equally well on a lower SKU or with fewer vCores - Check for stale, inactive, or low-traffic workloads that no longer require high performance tiers ## How to fix 5 ways to remove the waste. - Downsize the compute tier (DTUs or vCores) to better match observed usage - For Elastic Pools, reduce the total eDTUs/vCores and consider consolidating lightly used databases - For Managed Instances, assess whether the vCore allocation can be reduced or workloads refactored - Establish periodic reviews of resource utilization as part of database lifecycle management - Use performance insights to guide rightsizing decisions, independent of reservation or licensing strategies ## Documentation Vendor references for pricing and configuration. - [Azure SQL Database Pricing azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/azure-sql-database/) - [Performance Tuning Guidance for Applications and Databases - Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/performance-guidance?view=azuresql) - [Monitor Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/monitoring-sql-database-azure-monitor?view=azuresql) - [Serverless compute tier - Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview?view=azuresql) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure SQL CER-0164 ### [Overprovisioned Storage in Azure SQL Elastic Pools or Managed Instances](https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-storage-in-azure-sql-elastic-pools-or-managed-instances) Azure SQL deployments often reserve more storage than needed, either due to default provisioning settings or anticipated future growth. Over time, if actual usage remains low, these oversized allocations generate unnecessary storage costs.... Databases - Azure SQL CER-0264 ### [Suboptimal Use of Serverless Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-serverless-compute-for-azure-sql-database-4fe48) Serverless is attractive for variable or idle workloads, but it can become more expensive than Provisioned compute when database activity is high for long portions of the day. As active time increases, per-second compute accumulation... Databases - Azure SQL CER-0263 ### [Suboptimal Use of Provisioned Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-provisioned-compute-for-azure-sql-database-9bb83) Databases deployed on Provisioned compute incur continuous hourly charges even when workload demand is low. For databases that are active only briefly within an hour, or for limited hours per month, Serverless can provide significantly... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.