SQL Transactions duration and log size used
Let's say the log file size is 1 GB when you leave work at 5 pm and come back next morning to see it has grown to 5 GB. There is space is disk and frequent log backups are scheduled, but you want to know what caused the log to grow. In this case let's assume that nothing related to check db or index rebuild was scheduled. I am trying to find a way to look for these long running transactions and the ones which caused the log to grow so I can see if the transaction can be tweaked to make it smaller and faster. I want to be able to configure and save these transactions based on some parameters like duration and/or log size. An extended event would be great.