Is there a way to find out how much of the transaction log a specific transaction uses?
I have a database with simple recovery model and a log file with max size 500 MB. During our tests we ran into a "log file is full" situation, which is pretty strange, because our largest table is just 200 MB in size, we use only implicit transactions, we have no concurrent users and we don't change large amounts of data, apart from the occasional bulk insert which adds another 80 MB or so.
We can probably find the culprit by refining our application tests, but is there a way to find the offending statement through some SQL Server monitoring means?