π‘οΈ Azure SQL Database is underutilizedπ’
- Contextual name: π‘οΈ Database is underutilizedπ’
- ID:
/ce/ca/azure/sql-database/database-underutilized - Tags:
- π’ Policy with categories
- π’ Policy with type
- π’ Production policy
- Policy Type:
COMPLIANCE_POLICY - Policy Categories:
COST,PERFORMANCE
Statsβ
not available
Logicβ
- π§ prod.logic.yamlπ’
- π Azure SQL Databaseπ΄
- π Azure SQL Database - object.extracts.yaml
- π§ͺ test-data.json
Descriptionβ
Descriptionβ
This policy identifies Azure SQL Databases that appear to be underutilized. A database is considered underutilized if its performance and storage metrics remain below defined thresholds over the past 30 days. This enables organizations to pinpoint resources that may be over-provisioned relative to their actual workload.
The policy evaluates the following conditions:
- DTU-based models: Average DTU consumption is below 20% and maximum storage utilization is below 10%.
- vCore-based models: Average CPU utilization is below 20%, App Memory utilization is below 40% and maximum storage utilization is below 10%.
Databases may also be aggregated into Elastic Pools for collective management. Underutilized Elastic Pools are evaluated separately by a dedicated policy.
Rationaleβ
Provisioning databases with resources that significantly exceed workload requirements leads to unnecessary cloud costs. Identifying underutilized databases allows organizations to rightsize provisioned compute resources, update them to serverless compute model, or consolidate them into Elastic Pools, resulting in direct cost savings.
... see more
Remediationβ
Remediationβ
When an Azure SQL Database is identified as underutilized, two primary remediation strategies can be considered:
- Resize the database to a lower service tier.
- Migrate the database into an Elastic Pool for consolidated resource management.
- Convert a vCore-based database to Serverless to optimize for intermittent or unpredictable workloads.
Before making changes, confirm that the workload does not have periodic spikes or upcoming growth that may require the current configuration.
Resize the Databaseβ
From Azure CLIβ
az sql db update \
--resource-group {{resource-group-name}} \
--server {{server-name}} \
--name {{database-name}} \
[--edition {{Standard}}] \
[--capacity {{10}}] \
[--max-size {{250GB}}] \
[--family {{Gen5}}]From PowerShellβ
Set-AzSqlDatabase `
-ResourceGroupName "{{resource-group-name}}" `
-ServerName "{{server-name}}" `
-DatabaseName "{{database-name}}" `
[-Edition "{{Standard}}"] `
[-RequestedServiceObjectiveName "{{S0}}"] `
... [see more](remediation.md)
policy.yamlβ
Linked Framework Sectionsβ
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| πΌ Cloudaware Framework β πΌ Resource Right-Sizing | 22 | no data | |||
| πΌ Cloudaware Framework β πΌ Workload Efficiency | 26 | no data |