Trace Data Compare with SQL Response 1.3

[xexex]

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？

[priyasinha]

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

[Brian Donahue]

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:

[xexex]

We're using SQL 2000, is that a reason why information is missing?