troubleshooting Question

error log exploded because TL became FULL

Avatar of 25112
25112 asked on
Microsoft SQL ServerMicrosoft SQL Server 2005Microsoft SQL Server 2008
19 Comments1 Solution342 ViewsLast Modified:
the recovery mode was full and the Transaction log file became full, hence it started triggering the error

LogDate      ProcessInfo      Text
2011-08-30 04:50:04.820      spid91      Error: 9002, Severity: 17, State: 2.
2011-08-30 04:50:04.820      spid91      The transaction log for database 'Test905' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

several times a second.. the log has been fixed, but the error log file has become 30GB.

i ran xp_readerrorlog 1, and it is at 34million records and still it has only finished 20 hours of such logging..

is it possible to avoid this kind of logging. (just warn once and leave it). what is the best standard to handle this kind of errors which can blow the error log file?
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 19 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 19 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros