SQL Monitor Trace Profiler less details than SQL Response?
xexex
Posts: 56
I've compare SQL Monitor 2.1 and SQL Response 1.3 because I need to decide upgrade or not. However, when I obtain a dead lock record on SQL Monitor, I've found that it's difficult to troubleshoot, base on the report from SQL monitor compare with SQL Response. Here is an example:
The process 232 locked the record and process 271 was the victim. Both show the same information
When I look at the Profiler Trace of Process 232, I've found that some statement has not been shown
This also appear in Victim Process
In SQL Response, I found that Victim Process only wait for 5 seconds and than roll back, so I change the timeout value in SQL statement. However, SQL Monitor didn't show "Roll Back" statement in Profiler Trace, I can't found the problem.
The process 232 locked the record and process 271 was the victim. Both show the same information
When I look at the Profiler Trace of Process 232, I've found that some statement has not been shown
This also appear in Victim Process
In SQL Response, I found that Victim Process only wait for 5 seconds and than roll back, so I change the timeout value in SQL statement. However, SQL Monitor didn't show "Roll Back" statement in Profiler Trace, I can't found the problem.
Comments
Thanks for reporting this issue. We will investigate this and this will most probably be fixed in 2.2. release. I have logged this as SRP-2969.
Thanks,
Priya
Project Manager
Red Gate Software
https://www.red-gate.com/supportcenter/ ... onitor.htm
We are currently working on this issue as I write. This will be part of 2.3 release which is also due soon.
Thanks,
Priya
Project Manager
Red Gate Software