error log exploded because TL became FULL
Posted on 2011-09-06
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?