Insufficient Disk Space

During recovery, it is a rare but possible occurrence for the server to require additional log or data space. If additional space is unavailable and either the log or data files cannot grow, the server:

• Reports error message 9002 or 1105 in the Microsoft® SQL Server™ error log.
• Marks the database as suspect.
• Takes the database offline.

To resolve the 9002 error message and bring the database online

1. Free disk space on any disk drive containing the log file for the related database. Freeing disk space allows the recovery system to grow the log file automatically.
2. Reset the suspect status by executing sp_resetstatus.
3. Run recovery by executing DBCC DBRECOVER (database).

   Or

1. Free disk space on a different disk drive.
2. Move the transaction log files with an insufficient amount of free disk space to the disk drive in Step 1.
3. Detach the database by executing sp_detach_db.
4. Attach the database by executing sp_attach_db, pointing to the moved files.

   Or

• Add a log file to the suspect database and run recovery on the database by executing sp_add_log_file_recover_suspect_db.

To resolve the 1105 error message and bring the database online

1. Free disk space on any disk containing a file in the filegroup mentioned in the 1105 error message. Freeing disk space allows the files in the filegroup to grow.
2. Reset the suspect status by executing sp_resetstatus.
3. Run recovery by executing DBCC DBRECOVER (database).

   Or

1. Free disk space on a different disk drive.
2. Move the data files in the filegroup with an insufficient amount of free disk space to the disk drive in Step 1.
3. Detach the database by executing sp_detach_db.
4. Attach the database by executing sp_attach_db, pointing to the moved files.

   Or

• Add a data file to the suspect database and run recovery on the database by executing sp_add_file_recover_suspect_db.

See Also