SQL Server error 1101: Could not allocate a new page
SQL Server needed a new page in the filegroup and every data file is full and unable to grow. Free disk space or let the files grow.
- Error number
1101- Severity
- 17
- Category
- Memory, log and storage
What it means
Error 1101 is raised when SQL Server can't allocate a new page in a filegroup: all of its files are full, and autogrowth is off, a maximum size was reached, or the disk has no room. It is the page-level counterpart of 1105 and has the same fixes.
Common causes
- Data files with autogrowth disabled or a
MAXSIZEthat has been reached. - A full disk.
- The 10 GB database limit of SQL Server Express.
How to fix it
-
Check the files and how full the volume is.
SELECT f.name, f.size / 128 AS size_mb, vs.available_bytes / 1048576 AS disk_free_mb FROM sys.database_files AS f CROSS APPLY sys.dm_os_volume_stats(DB_ID(), f.file_id) AS vs;
-
Allow growth or add a file, as for error 1105.
ALTER DATABASE SalesDb MODIFY FILE (NAME = SalesDb_data, MAXSIZE = UNLIMITED);
Related errors
1105Filegroup is full, cannot allocate9002Transaction log for database is full1114MySQL: The table is fullORA-01653Oracle: unable to extend table in tablespace
More memory, log and storage errors
701Insufficient memory in resource pool8645Timeout waiting for memory resources8623Query processor ran out of resources1204Cannot obtain a LOCK resource
The code and message text are from the Microsoft Database Engine events and errors reference. Browse the full SQL Server error list or search every database error.
Work on SQL Server in SQLly
A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for SQL Server and the other databases you use.