# Overprovisioned Compute Tier in Azure SQL Database

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-compute-tier-in-azure-sql-database

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Overprovisioned Compute Tier in Azure SQL Database

## Explanation

Azure SQL Database resources are frequently overprovisioned due to default configurations, conservative sizing, or legacy requirements that no longer apply. 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.

## Relevant Billing Model

- Billed based on provisioned compute resources (DTUs or vCores), regardless of usage

- Storage billed per GB/month

- Higher tiers (e.g., Business Critical, Premium) incur significantly greater cost

- Charges apply whether the database is actively used or idle

## Detection

- 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

## Remediation

- 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

## Relevant Documentation

- [Azure SQL Database Pricing](https://azure.microsoft.com/en-us/pricing/details/azure-sql-database/)

- [Performance Guidance for Azure SQL Database](https://learn.microsoft.com/en-us/azure/azure-sql/database/performance-guidance-overview)

- [Monitor resource utilization](https://learn.microsoft.com/en-us/azure/azure-sql/database/monitoring-sql-database)

[Submit Feedback](https://hub.pointfive.co/inefficiencies/overprovisioned-compute-tier-in-azure-sql-database)

## At a glance

Reference

CER-0028

Cloud provider

Azure

Service

Azure SQL

Category

[Databases](https://www.pointfive.co/efficiency-hub/service-category/databases)

Inefficiency type

Overprovisioned Resource

## Contributed by

- Balazs Engedi 

### Balazs Engedi

FinOps Specialist @ KPN

[LinkedIn](https://www.linkedin.com/in/engedib/)

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.