Tracking down log file growth with SQL Monitor
Could someone explain how I can use SQL Monitor to identify the queries that caused large log file growth on sql server.
An incident occurred yesterday where the log file grew from 60Gb to 116Gb. The were no large data imports at the time.
The database in question uses full detail logging. It's also set up for log shipping so the log file won't automatically get shrunk.
I understand that I can rewind to the time the event happened and I can see some long running queries but a long running query isn't necessarily going to grow the log.
I appreciate your feedback.