// SQL Server error reference

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
Error message
Could not allocate a new page for database '%.*ls' because the '%.*ls' filegroup is full due to lack of storage space or database files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

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 MAXSIZE that has been reached.
  • A full disk.
  • The 10 GB database limit of SQL Server Express.

How to fix it

  1. 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;
  2. Allow growth or add a file, as for error 1105.

    ALTER DATABASE SalesDb MODIFY FILE (NAME = SalesDb_data, MAXSIZE = UNLIMITED);

Related errors

More memory, log and storage errors

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.

// fewer errors, faster fixes

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.