Unanswered: find transaction that generated 4 Go in journal file
We are using SQL Server with logshipping.
I noticed in the last two days the presence of 2 bigs journal files
(about 2Go each, transfered from primary to secondary ).
I want to know if there is a way to see what was the operation that lead to have this to big 2 log files
(sql statement or transaction... : with Oracle for instance, if we have chance, we can find this kind of info in
a dynamic views by the name of : v$sqlarea...)...