December 23, 2010 at 8:26 am
Comments posted to this topic are about the item What Is Filling Up The Transaction Log
February 18, 2011 at 10:43 am
I'd suggest that the code for [Log Used %] be changed to:
[font="Courier New"], CAST(CAST(CAST(lu.cntr_value AS FLOAT) / CAST(ls.cntr_value AS FLOAT) AS DECIMAL(18, 4)) * 100 AS DECIMAL(18, 2)) AS [Log Used %]
[/font]
This gives you an additional 2 digits before doing your left shift so you don't always end up with results .00.
February 16, 2012 at 7:25 am
Title was full of promise, but we need more.
Ideally, we want to be able to determine what statements caused the log to grow so suddenly (and who issued the statements) and we want to do this automatically, not by running a query. i.e. at the time there is "excessive log file growth" alert the DBA providing a list of user-statements currently executing.
The tools and DMVs are out there but unfortunately do not provide a full picture (who, what, when, sql statements running). I think Profiler comes to the closest (Events "Log File Auto Grow" & "SQL:BatchCompleted") but even that involves monitoring and examining, not automatically alerting.
September 24, 2012 at 7:42 am
I have a scenario here:
On my TEMPDB, the log reuse wait description shows " Active_transaction".
Then I checked DBCC OPENTRAN('tempdb') . I got message showing there are no open transactions. Then I also queried:
select * from sys.dm_tran_active_transactions
I see some four 6 worktables. I don't know about these tables. Now how can I change my tempdb state to "Nothing".
September 24, 2012 at 8:02 am
When I restarted the server, tempdb - logreuse wait description showing 'Nothing'. So, is this the only way we need to do?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply