1101: Could not allocate a new page because of insufficient disk space in filegroup
SQL ServerWhat does it mean?
SQL Server tried to allocate a new page for an object, but the filegroup has insufficient disk space. The data files can neither grow nor find a free page, so the write fails.
Why does it happen?
The disk holding the data file is full; autogrow is disabled on the file or MAXSIZE has been reached; or every file in the filegroup has hit its size ceiling. Common during large INSERTs/index builds.
How to fix it
Free space on the disk or add space to the filegroup. Grow the file or enable autogrow: ALTER DATABASE db MODIFY FILE (NAME = logical_name, SIZE = 20GB, MAXSIZE = UNLIMITED, FILEGROWTH = 512MB); Alternatively, add a new file to the filegroup (on another disk). To see file usage, check sys.database_files and free space with DBCC SQLPERF.
More from this engine
- 601Could not continue scan with NOLOCK due to data movement
- 50000Custom error raised with RAISERROR
- 3902The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION
- 3729Cannot DROP because it is being referenced by object
- 3961Snapshot isolation transaction failed because the object was modified by a DDL statement
- 1785Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths
- 9421XML parsing: illegal xml character