SQL Server Error 1105

Why it happens

Error 1105 is about the DATA file, not the log file. It means SQL Server tried to allocate a new page for a table or index inside a filegroup and there was nowhere to put it. Unlike error 9002, which fires when the transaction LOG file is full, 1105 fires when the data file (usually in the PRIMARY filegroup) has run out of room.

The message names the object, the database, and the full filegroup: the 'PRIMARY' filegroup is full. A data file only grows when autogrowth is enabled and there is space to grow into, so 1105 appears when one of three things is true.

Common causes are that the data file reached its configured maximum size or has autogrowth disabled, the disk holding the file is physically full so it cannot grow further, or a filegroup other than PRIMARY that a table is mapped to has filled up. The error is severity 17, meaning the server ran out of a resource; the statement fails and rolls back rather than corrupting anything.

Examples

The data file hit its maximum size

-- Data file capped at 100 MB with autogrowth off.
-- A large insert exhausts the remaining pages.
INSERT INTO dbo.Orders (customer_id, total)
SELECT customer_id, total FROM staging.Orders;

Msg 1105, Level 17, State 2, Line 3
Could not allocate space for object 'dbo.Orders' in database 'AppDb' because the 'PRIMARY' filegroup is full.

Check file sizes and free space inside each file

SELECT name AS logical_name,
       type_desc,
       size / 128.0 AS size_mb,
       CAST(FILEPROPERTY(name, 'SpaceUsed') AS INT) / 128.0 AS used_mb,
       (size - CAST(FILEPROPERTY(name, 'SpaceUsed') AS INT)) / 128.0 AS free_mb,
       max_size,
       growth
FROM sys.database_files;

-- No error. This shows which data file is full and
-- whether it can still grow (max_size and growth columns).

Check overall space use with DBCC SQLPERF

-- Log space use across databases (companion check).
DBCC SQLPERF(LOGSPACE);

-- For data files, inspect free space per file:
DBCC SHOWFILESTATS;

-- No error. Use these to confirm whether the shortage is
-- in the data file (1105) or the log file (9002).

How to fix it

ALTER DATABASE AppDb
    MODIFY FILE (
        NAME = 'AppDb',
        FILEGROWTH = 256MB,
        MAXSIZE = 50GB
    );

ALTER DATABASE AppDb
    ADD FILE (
        NAME = 'AppDb_2',
        FILENAME = 'E:\\SqlData\\AppDb_2.ndf',
        SIZE = 2GB,
        FILEGROWTH = 256MB
    ) TO FILEGROUP [PRIMARY];

-- Remove old rows, then reclaim their space.
DELETE FROM dbo.Orders WHERE order_date < '2020-01-01';

ALTER INDEX ALL ON dbo.Orders REBUILD;

ALTER DATABASE AppDb
    MODIFY FILE (
        NAME = 'AppDb',
        FILENAME = 'F:\\SqlData\\AppDb.mdf'
    );

-- Then copy the file to the new path and:
ALTER DATABASE AppDb SET OFFLINE;
ALTER DATABASE AppDb SET ONLINE;

How to prevent it

Monitor data file free space and disk capacity so you see a filegroup filling up before it stops writes. Alert on percent used per file and on drive free space, not just on total database size.

Set sensible autogrowth increments and a realistic MAXSIZE on every data file, and plan capacity ahead of large loads. Because 1105 and 9002 both stem from running out of room, treat data and log growth together when you size a database. For how transactions interact with these files, see SQL transactions and ACID explained.

Common questions