# Suboptimal use of provisioned compute for Azure SQL Database Canonical: 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. By: Benjamin van der Maas Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Suboptimal Use of Provisioned Compute for Azure SQL Database The short version Databases deployed on Provisioned compute incur continuous hourly charges even when workload demand is low. [Benjamin van der Maas](https://www.linkedin.com/in/benjamin-van-der-maas-71168466/) Manager, Cloud FinOps @ Johnson & Johnson 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-0263 Type Suboptimal Tier or SKU ## Explanation Why the waste happens and who it affects. For databases that are active only briefly within an hour, or for limited hours per month, Serverless can provide significantly lower cost because it bills per second for the compute used, never less than the configured minimum vCores and memory while the database is online, and only for storage while the database is auto-paused (auto-pause is supported only in the General Purpose tier). The economic break-even point between Provisioned and Serverless depends on workload activity patterns. If monthly active time falls below the conceptual break-even range, Serverless is more cost-effective. If active time regularly exceeds that range, Provisioned may be more appropriate. This inefficiency typically appears when teams default to Provisioned compute without evaluating workload behavior over time. ## Billing model The pricing dimensions that drive this cost. Provisioned compute is billed per vCore-hour regardless of usage. Serverless compute is billed per second for the vCores and memory used, with a floor at the configured minimum vCores and memory while the database is online, plus storage; compute charges stop only while the database is auto-paused, which is supported only in the General Purpose tier. Azure Hybrid Benefit and reservation discounts do not apply to serverless, so compare against the discounted provisioned price when estimating the break-even point. Selecting Provisioned for workloads with low or sporadic utilization results in paying for unused capacity. ## How to detect 4 checks to find it in your estate. - Review whether database activity is intermittent or consistently low throughout the day - Assess whether monthly active time is substantially lower than the equivalent cost of Provisioned compute - Evaluate whether workload patterns include extended idle periods suitable for auto-pause - Check for development, testing, or sporadic workloads that do not require continuous compute availability ## How to fix 4 ways to remove the waste. - Move the database to the Serverless compute tier when workloads are intermittent or have low active time - Use Serverless auto-pause capabilities to eliminate compute charges during idle periods - Periodically reassess compute model selection as application usage patterns evolve - Apply workload profiling to ensure that Serverless performance meets application needs before migration ## Documentation Vendor references for pricing and configuration. - [Serverless compute tier - Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview?view=azuresql) - [Serverless compute tier billing - Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-billing?view=azuresql) - [Pricing - Azure SQL Database Single Database azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/azure-sql-database/single/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - 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-0239 ### [Azure Hybrid Benefit Not Enabled on SQL Databases](https://www.pointfive.co/efficiency-hub/inefficiencies/azure-hybrid-benefit-not-enabled-on-sql-databases-41927) Azure Hybrid Benefit allows organizations to apply existing SQL Server licenses with Software Assurance or qualifying subscriptions to Azure SQL Databases. When this configuration is missed or not enforced, workloads continue to incur... Databases - Azure SQL CER-0194 ### [Overbilling Due to Frequent Tier Switches in DTU Model](https://www.pointfive.co/efficiency-hub/inefficiencies/overbilling-due-to-tier-switches-and-allocation-overlaps-in-dtu-model) Workloads that frequently scale up and down within the same day-whether manually, via automation, or platform-managed-can encounter hidden cost amplification under the DTU model. Azure SQL Database bills each hour at the highest service... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.