How can we help you today? How can we help you today?

SQL Monitor Trace Profiler less details than SQL Response?

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
sqlmonitordeadlockdetai.jpg

sqlresponsedeadlockdeta.jpg

When I look at the Profiler Trace of Process 232, I've found that some statement has not been shown
sqlmonitordeadlocksqlpr.jpg

sqlresponsedeadlocksqlp.jpg


This also appear in Victim Process
sqlmonitordeadlocksqlpr.jpg

sqlresponsedeadlocksqlp.jpg

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.
xexex
0

Comments

3 comments

Sort by
  • priyasinha
    Hi,

    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
    priyasinha
    0
  • xexex
    SRP-2969 doesn't fix in 2.2 yet?
    https://www.red-gate.com/supportcenter/ ... onitor.htm
    xexex
    0
  • priyasinha
    Hi,

    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
    priyasinha
    0

Add comment

Please sign in to leave a comment.