How to fix Error 1132 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: Error 1132 – Elastic Pool Storage Limit Exceeded

Why This Error Happens

This error occurs when the combined data storage consumed by all databases within an Azure SQL Elastic Pool (or a SQL Server 2025 instance configured with elastic pool semantics) exceeds the maximum storage threshold defined for that pool’s service tier. This is typically caused by unmonitored data growth, large transaction log files not being truncated, or a misconfigured pool size that does not match the actual workload requirements. Additionally, temporary spikes from bulk insert operations, index rebuilds, or orphaned data files can push the pool past its provisioned MB limit before autogrowth settings or tier upgrades are applied.

Step-by-Step Resolution Guide

Step 1: Identify Current Storage Consumption

  • Open SQL Server Management Studio (SSMS) and connect to the instance hosting the elastic pool.
  • Run the following query to check per-database space usage:
  SELECT DB_NAME(database_id) AS DatabaseName, 
         SUM(size) * 8 / 1024 AS SizeMB
  FROM sys.master_files
  GROUP BY database_id
  ORDER BY SizeMB DESC;
  • Cross-reference results against the Azure Portal under SQL elastic pools > [Pool Name] > Overview > Storage Used.

Step 2: Clear Unnecessary Data and Reclaim Space

  • Navigate to Database > Tasks > Shrink > Database in SSMS for the largest offending database.
  • Alternatively, run DBCC SHRINKDATABASE (YourDatabaseName, 10); to reclaim unused allocated space.
  • Check for bloated transaction logs using DBCC SQLPERF(LOGSPACE); and switch recovery model to Simple temporarily if logs are the culprit.

Step 3: Increase the Elastic Pool Storage Limit

  • Go to the Azure Portal (or Windows Admin Center if managing locally via Windows Server 2025) and select the affected Elastic Pool.
  • Under Configure, increase the Max Storage (MBs) slider to a value higher than current usage, or upgrade the service tier (e.g., Standard to Premium) to unlock higher storage ceilings.
  • Click Save and allow 5–10 minutes for the scaling operation to propagate across all pooled databases.

Step 4: Redistribute Databases Across Pools

  • If storage limits are a tier-wide constraint, open Elastic Pool Manager and move lower-priority databases to a separate pool with its own storage allocation.
  • Use ALTER DATABASE [DBName] MODIFY (SERVICE_OBJECTIVE = ELASTIC_POOL(name = [NewPoolName])); to migrate a database out of the saturated pool.

Alternative or Verification Steps

  • Re-run the SUM(size) query from Step 1 and confirm the total is now below the new MB threshold shown in the Azure Portal overview pane.
  • If the error persists immediately after resizing, restart the SQL Server service (Restart-Service MSSQLSERVER in PowerShell) to force the engine to re-read the updated pool configuration.