Trace Data Compare with SQL Response 1.3

SQL Server performance monitoring and alerting

Trace Data Compare with SQL Response 1.3

Postby xexex » Thu Mar 07, 2013 4:39 am

I'm using SQL Response 1.3. I use it to troubleshoot the deadlock, it help me alot.
I've tried SQL monitor, it's a powerful tool to monitor SQL performance. However, compare with SQL Response, it provide less information about trace record. For exampe, SQL response can capture the statement between BEGIN TRAN and COMMIT/ ROLLBACK", but SQL monitor always miss it. Moreover, error message such as "1205" will be indicated as red color in SQL response, but not in SQL monitor.
It seem that SQL monitor is focus on SQL performance but not on trace data .

I really want to upgrade to SQL Monitor 3.0, the performance analysis is great that SQL response can't provide it. Will SQL monitor focus on trace data in future version, or I can obtain this feature from other Redgate product?
xexex
 
Posts: 41
Joined: Thu Jun 24, 2010 5:50 am

Postby priyasinha » Fri Mar 08, 2013 1:50 pm

Hello,

Thanks for your message.

As far as I am aware the implementation of trace is very similar between SQL Response 1.3 and SQL Monitor 3. Unfortunately, we have not looked at the code for SQL Response 1.3 for few years now so we wont be able to tell you the exact differences. But there is much more functionality in SQL Monitor V 3 than in SQL Response 1.3.

Thanks,
Priya
priyasinha
 
Posts: 532
Joined: Wed Jan 03, 2007 5:02 pm

Postby Brian Donahue » Fri Mar 08, 2013 4:40 pm

Hi,

You should be getting at least the same amount of information - SQL Monitor turns on a trace flag that prints deadlock information to the SQL Server ERRORLOG and we get that information. I did a simple test and it showed me this:
Code: Select all
Deadlocked processes:
 57
Victim process:
59
Object blocked:
Row


Deadlocked processes
SPID
Victim
Lock details
Statement type
 57
dbid: 2, file id: 1, page no.: 1027, row no.: 2
UPDATE Line #: 10
 59
Victim process

dbid: 2, file id: 1, page no.: 1029, row no.: 2

UPDATE Line #: 10
SQL query fragment:
Language Event: --QA window £1
BEGIN TRAN
UPDATE ##temp1 SET col1 = 4 WHERE col1 = 3

 WAITFOR DELAY '0:0:05'

--this proc is holding lock on ##temp1
If you do not get the query fragment, you may be using an unsupported version of SQL Server or possibly there is a problem with the connection to the SQL Server from the base monitor.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby xexex » Fri Mar 15, 2013 3:18 am

We're using SQL 2000, is that a reason why information is missing?
xexex
 
Posts: 41
Joined: Thu Jun 24, 2010 5:50 am


Return to SQL Monitor 3

Who is online

Users browsing this forum: No registered users and 0 guests