September 10, 2014 at 7:01 am
This morning, I walked into a database that was unusable due to a full transaction log...
(Strike 1, my Alert for full logs didn't work, I think I have it configured wrong)
I got the customer back in by expanding the TLog and started to dig into what might've caused the problem.
First issue, the log file is set to auto-grow, and has a fairly high max size (which it was nowhere near reaching.)
(Strike 2, the log was configured to grow by 1MB... Also now corrected to a more rational number)
I took a look in the SQL Logs, the Windows Application and System logs, and saw no reason for the system to have not grown the TLog file. If anyone has any ideas as to why it might've done this, it would be appreciated.
Thanks,
Jason
September 10, 2014 at 9:13 am
Quote on the drive? Other than that, no reason for SQL not to try. Nothing in SQL Error log?
September 10, 2014 at 9:48 am
No quotas on the drives.
Thank you for suggesting the error log, just ran a query I've got that reads the trace files for auto-growth events. Interestingly, the log auto-grew a couple times, hit 3:30am (about) which is when the SQL Log started reporting the log full.
Unfortunately, I don't have a record of what the growth and size settings were before this morning, but I'm wondering if I might've had a (normally) reasonable limit on the size of the TLog. Turns out, since yesterday some time, our backup team had disabled the backups (normal and TLog) for this server (They were thinking in Oracle terms when I requested backups be suspended for another DB on this same server, the DB is in a decommision process)...
Hmmm.
Thanks Steve!
September 10, 2014 at 10:02 am
You are welcome and sorry I don't have anything else. If you figure it out, I'd be interested in knowing what happened.
September 14, 2014 at 8:18 pm
Was the auto growth restricted to a specific size and it reached that size?
Regards,
SQLisAwe5oMe.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply