Deployment issue: I've tried to deploy a SQL Elastic Pool (running SQL Server (PaaS)), but it fails due to storage limit message. In the Azure Portal it's using the same settings as in the deployment pipeline. I've checked every SQL Database, it's well below the actual consumed disk space. Any idea's what is going wrong? Perhaps a way to identify which database is causing the issues?

Exceptions: What did recently occur is one of the databases had peaked 100% CPU performance for several weeks. However the database usage in the portal is below 100 MB since I couldn't take this database offline, but that seems OK.

Pool settings:

• Service Tier: Standard (Budget Friendly)
• eDTU: 100
• Data max size (GB): 200

Databases:

• All databases combined are below 100 GB used size
• Per Database Settings: 0 - 100 DTU

Deployment pipeline issue for SQL Elastic Pool:

{
  "code":"ElasticPoolDecreaseStorageLimitBelowUsage",
  "message":"The storage limit for the elastic pool 'sql-elasticpool-prod' does not provide sufficient storage space for its databases. Please increase the storage limit or move databases out of the pool."
}

Note: I've also seen this topic Azure SQL Server Error : The elastic pool has reached its storage limit. The storage usage for the elastic pool cannot exceed (204800), but didn't found the solution there.

Deployment issue: I've tried to deploy a SQL Elastic Pool (running SQL Server (PaaS)), but it fails due to storage limit message. In the Azure Portal it's using the same settings as in the deployment pipeline. I've checked every SQL Database, it's well below the actual consumed disk space. Any idea's what is going wrong? Perhaps a way to identify which database is causing the issues?

Exceptions: What did recently occur is one of the databases had peaked 100% CPU performance for several weeks. However the database usage in the portal is below 100 MB since I couldn't take this database offline, but that seems OK.

Pool settings:

• Service Tier: Standard (Budget Friendly)
• eDTU: 100
• Data max size (GB): 200

Databases:

• All databases combined are below 100 GB used size
• Per Database Settings: 0 - 100 DTU

Deployment pipeline issue for SQL Elastic Pool:

{
  "code":"ElasticPoolDecreaseStorageLimitBelowUsage",
  "message":"The storage limit for the elastic pool 'sql-elasticpool-prod' does not provide sufficient storage space for its databases. Please increase the storage limit or move databases out of the pool."
}

Note: I've also seen this topic Azure SQL Server Error : The elastic pool has reached its storage limit. The storage usage for the elastic pool cannot exceed (204800), but didn't found the solution there.

• sql-server
• azure
• azure-sql-database
• azure-elasticpool

• Have you checked if any database has unexpected space allocations or auto-growth enabled? – Pratik Lad Commented 2 days ago
• Where can I check auto-growth? The space allocation is currently quite normal. There were only a lot of errors, but that didn't have much difference in the used SQL database space. – NetDev Commented yesterday

1 Answer 1

The root cause of the error is a mismatch between the allocated max size of your database and the SQL Elastic Pool’s max size (200GB).

{
  "code":"ElasticPoolDecreaseStorageLimitBelowUsage",
  "message":"The storage limit for the elastic pool 'sql-elasticpool-prod' does not provide sufficient storage space for its databases. Please increase the storage limit or move databases out of the pool."
}

• Even though actual storage in your database usage is <100GB, Azure enforces limits based on allocated capacity.

I've tried replicating your issue by setting up an empty database and an Azure SQL Elastic Pool. (with the same stats provided)

Here’s how I verified the actual storage capacity of both using Bash commands:

For Database:

az sql db show --resource-group **resourse_group_name** --server **server_name** --name **db_name** --query "{Database:name, MaxSize:maxSizeBytes, Status:status}" --output table

For Elastic Pool Server:

az sql elastic-pool show --resource-group **resourse_group_name** --server **server_name** --name **elastic_pool_name** --query "{ElasticPool:name, MaxSize:maxSizeBytes, eDTU:sku.capacity}" --output table

As you can see that the database size is larger than Elastic Pool's allowed storage. This is the core issue due to which you are facing the error.

Options to resolve the error :

1. Increasing SQL Elastic Pool Storage Limit:

az sql elastic-pool update --resource-group trial --server elastic-server --name sql-elastic-pool --max-size 300GB 

2. Reducing Database Size:

az sql db update --resource-group trial --server elastic-server --name elastic-db --max-size 150GB

If your database's allocated size exceeds the Elastic Pool's limit, reduce it if larger size isn't required.