asked
How to read the Transaction Log SQL 2000
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! Maripili
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][1] [are][2] a [few][3] [examples][4] [from][5] [SSC][6]. [1]:
http://www.sqlservercentral.com/scripts/63648/ [2]:
http://www.sqlservercentral.com/scripts/65384/ [3]:
http://www.sqlservercentral.com/scripts/67251/ [4]:
http://www.sqlservercentral.com/scripts/30819/ [5]:
http://www.sqlservercentral.com/scripts/31482/ [6]:
http://www.sqlservercentral.com/scripts/32000/
Thank you very much. The DBA before me, let somethink like that, and we have it on a table and give them the name and access to see it, but they still want to se the log file. There's the reason why I wan't to know if it's some tool for that. Do you have the names of this tools? may be I can use them to demostrate what they can see in this tools....
Apex has a tool that can do it:
http://www.apexsql.com/sql_tools_log.aspx. But again, you can't stress enough, this will show you which queries completed. That's all. It won't show you any that failed, it won't show which query was blocking which, it's extremely limited. The transaction log contains, transactions. It doesn't have all sorts of long running troubleshooting capacity built in.
