Trace Data Compare with SQL Response 1.3

• 
  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 March 08, 2013 07:50

  - 0 +
• 
  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:

  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 March 08, 2013 10:40

  - 0 +
• 
  We're using SQL 2000, is that a reason why information is missing?

  xexex March 14, 2013 22:18

  - 0 +

Add comment

Please sign in to leave a comment.