Is it possible to analyze SQL Server 2005 Transaction logs using LogParser 2.2? If not, what is the alternative? Red Gate's tool only analyzes SQL Server 2000 and Lumigent's Log Parser is no where to be found.
TIA ramesh
+1
A:
The reason is that the log is in a proprietary and different format for 2005/2008 and MSFT has not released the specs so there are no log parsers yet that work for 2005 and 2008
SQLMenace
2009-02-03 22:10:08
so am I outa luck?
rams
2009-02-03 22:13:35
A:
What information are you trying to get from the transaction log? Perhaps there is another way.
mrdenny
2009-02-04 01:46:18
our SQL Server pegged the CPU at 75%, used > 7Gig RAM and refused all connections. Had to reboot. Trying to figure out if transaction log can provide any clue
rams
2009-02-04 14:31:32
A:
If your DB is consuming 75% and your connections are all in use, you might start by checking out the activity monitor and seeing what processes are churning and/or running the profiler before you worry about the log files.
edit: sorry, initially missed the part where you mentioned you rebooted.
Jason
2009-02-04 23:37:55
unfortunately had to reboot so could not attach activity monitor. If no new connections are possible, then I am not sure if profiler can be attached to the server
rams
2009-02-05 21:08:28
A:
You would need to attach SQL Profiler to the SQL Instance after the problem has started, but before the SQL Server stops users from connecting. Try pausing the service for a few minutes to allow some of the connections to finish and disconnect then unpause the service and see if profiler can connect.
Also try running SQL Profiler locally on the server. While remote connections may not work, local connections may.
mrdenny
2009-02-06 08:00:45
A:
There is a product that does what I think you are after, unfortunately its not cheap. It lets you monitor the transaction logs for SQL 2005/2008. I would love something open source but cant find anything yet.
Dean
2009-06-17 09:25:45