// SQL Server error reference

SQL Server error 1105: Filegroup is full, cannot allocate

A data file in the filegroup reached its maximum size or the disk is full, so SQL Server can't allocate space for the table or index.

Error number
1105
Severity
17
Category
Memory, log and storage
Error message
Could not allocate space for object '%.*ls'%.*ls in 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

Tables and indexes live in filegroups made of one or more data files. When none of the files in the filegroup has free space and none can grow, because autogrowth is off, a MAXSIZE was reached or the disk is full, inserts and index builds fail with 1105. Error 1101 is the same condition when allocating a new page. In SQL Server Express, the 10 GB database size limit causes it too.

Common causes

  • Autogrowth disabled, or MAXSIZE set on the data files.
  • The disk or volume holding the data files is full.
  • SQL Server Express reached its 10 GB per-database limit.
  • An index rebuild or large load that temporarily needs much more space.

How to fix it

  1. Check file sizes, limits and growth settings.

    SELECT name, physical_name, size / 128 AS size_mb,
           CASE max_size WHEN -1 THEN NULL ELSE max_size / 128 END AS max_mb,
           growth, is_percent_growth
    FROM sys.database_files;
  2. Let the file grow, or raise its limit.

    ALTER DATABASE SalesDb MODIFY FILE (NAME = SalesDb_data, MAXSIZE = UNLIMITED, FILEGROWTH = 1GB);
  3. Add a file on another volume if the disk is full.

    ALTER DATABASE SalesDb ADD FILE (NAME = SalesDb_data2, FILENAME = N'E:\Data\SalesDb_data2.ndf', SIZE = 10GB, FILEGROWTH = 1GB) TO FILEGROUP [PRIMARY];
  4. Free space by archiving or purging old data, then rebuild fragmented indexes.

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.