Transaction log for database is ful, See log_reuse_wait_desc

Author Johnny Josefsson on August 3, 2010 | Print | Bookmark

These errors in SQL/Windows indicated in our case that the config for "autogrowth" of the log file was disabled and the log needed to grow beyond the inital size.

SQL SERVER LOG
Date  2010-08-03 00:10:02
Log  SQL Server (Current - 2010-08-03 00:10:00)
Source  spid53
Message
The transaction log for database 'logs' is full. To find out why space in the log cannot
be reused, see the log_reuse_wait_desc column in sys.databases

WINDOWS APPLICATION LOG
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 9002
Date:  2010-08-03
Time:  00:20:01
User:  DOMAIN\svc-sql_server
Computer: SERVER
Description:
The transaction log for database 'logs' is full. To find out why space in the log cannot be
reused, see the log_reuse_wait_desc column in sys.databases 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 11 00 00 00   *#......
0008: 0d 00 00 00 53 04 45 00   ....S.E.
0010: 2d 00 43 00 30 04 31 00   R.V.E.R.
0018: 2d 00 53 00 52 00 54 00   S.E.R.V.
0020: 31 00 37 00 00 00 08 00   E.R.....
0028: 00 00 6c 00 6f 00 67 00   ..l.o.g.
0030: 73 00 00 00               s...

1. Open Enterprise Manager/Management Console
2. Drill down to the database with the problem
3. Properties on database
3. Files
4. Database files
5. Find line with the log file for the DB, verify the config for column "autogrowth"
6. Configure it to something sutiable for this specific database and it's usage.

Was this article helpful?

Yes No

Category: Windows, MS SQL

Last updated on August 3, 2010 with 2215 views