Resolve SQL Server Error 1105 - "Primary filegroup is full"

SQL Server Error 1105 – Severity 17 State 2

Topics

Error Description Error Message Causes Resolution Tipso Attach/Detach the Databaseo Set Recovery Model

Conclusiono More Information

Error Description

Sometimes, when having enough disk space for the database and doing some transactions into it, the SQL Server displays error 1105.

“SQL error 1105 can be occurred in logs or in Event Viewer”

Error Message

Error : 1105, Severity: 17, State: 2

“Could not allocate space for object '%.*ls' in database '%.*ls' because the '%.*ls' filegroup is full”

Note: State: 2 shows the transaction log is full

Causes

The size of database is big and sometimes holds artificial limitation on its size, usually applied by a previous host’s administrator.

The database is not set on Simple Recovery Model

The temporary database size is running out of space.

Resolution Tips

Attach/Detach the Database Set Recovery Model

Attach/Detach the Database

Move data files to another drive in a filegroup with insufficient free disk space.

Execute sp_detach_db to detach the database. Execute sp_attach_db to attach the database,

pointing to the moved files.

Set Recovery Model

Make sure your Recovery model is set to Simple in order to remain the log file from increasing so fast.

Conclusion If you still getting the SQL Error 1105 after

applying these operations on your database, then you can shrink MS SQL transaction log file and get the same resolution.

More Information