er.mayankshukla (8/23/2014)
I would not suggest you to use DBCC ShrinkDatabase, but should see the query which is creating this.In one of my projects I observed such a behaviour when I was using a bulk delete which caused log file to increase tremendously.
Try to use fn_dblog and try to find which transaction created maximum log
Quick question, have you looked into the sys.dm_tran* views to identify the transaction activities?
😎