Hi again, there's another of my doubts...
I was looking for some tool or something that give me results to read the transaction log. I found in a lot of places that it can't be, and found some tools that doesn't give me the result I want.
Why I need to read it? well actually, at the company where I'm working, the developers wan't to see the querys that produce a block and for example how long it takes. I said, you can run a trace, but they want to see the past blocks and all of that. For example two days ago, they asked me if I can see the query, the machine where the query came from and the user who did that in the log.
So, I need to know if it's possible and how.
Thanks a lot for your answere's!
asked Sep 20 '10 at 07:45 AM in Default
There are a few third party tools that can read the log, but the problem you're going to run into is that you won't know which procedure was causing blocking. You'll just know which ones were running for a long time. That's not the same thing. Instead, you should look at some of the blocking monitoring scripts that are available. I'd put these in place instead of even using a trace (although I'd use a trace too). Here are a few examples from SSC.
answered Sep 20 '10 at 07:55 AM
Grant Fritchey ♦♦