ea15ffd4   
   From: esquel@sommarskog.se   
      
   xo (xo5555ox@gmail.com) writes:   
   > I suspect the processes encountered blocking instead of deadlocking   
   > since SQL server error log did not capture any info. But the   
   > application folks keep insisting there was deadlocking and provided   
   > the following log info from the application side.   
      
   The error message sure looks like a deadlock to me.   
      
   I don't know why it was captured. Maybe they are running against several   
   instances, the deadlock was another instance?   
      
   You can easily verify that your configuration is working. Create this   
   table:   
      
       CREATE TABLE test(a int NOT NULL PRIMARY KEY)   
      
   Then run in two windows:   
      
      BEGIN TRANSACTION   
      SELECT MAX(a) FROM test WITH (HOLDLOCK)   
      WAITFOR DELAY '00:00:10'   
      INSERT test(a) VALUES(19)   
      ROLLBACK TRANSACTION   
      
   Yet an alternative to capture deadlock information is through traces   
   or event notifications.   
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
   SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)