| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | |
|---|---|---|---|---|---|---|---|---|---|
MSSQLSERVER_9002 |
MSSQLSERVER_9002 |
MashaMSFT |
mathoma |
04/04/2017 |
sql |
supportability |
reference |
|
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 9002 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | LOG_IS_FULL |
| Message Text | The transaction log for database '%.*ls' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases. |
The database log is out of space. These are reasons why the log can run out of space
- Log not being truncated
- Disk volume is full
- Log size is set to a fixed maximum value or autogrow is disabled)
- Replication or availability group synchronization that is unable to complete
The log_reuse_wait_desc column in sys.databases (Transact-SQL) describes why space in the log cannot be reused.
A very common solution to this problem is to ensure transaction log backups are performed for your database which will ensure the log is truncated. If no recent transaction log history is indicated for the database with a full transaction log, the solution to the problem is straightforward: resume regular transaction log backups of the database.
For detailed information on resolving this error, see Troubleshoot a Full Transaction Log (SQL Server Error 9002).