not all deadlocks captured by Extended events and erorrlog

• ebooklub

  Hall of Fame

  Points: 3905

  More actions

  January 16, 2019 at 10:21 am

  #382592

  SQL 2012 
  DBCC TRACEstatus (1222,-1) -- show trace is on globally
  Extend events also set to capture  "database_xml_deadlock_report"

  SQL agent job report deadlock
  Date        1/16/2019 7:10:00 AM
  Log        Job History ( Load Prices)
  Step ID        1
  Server        myserver
  Job Name     Load Prices
  Step Name        step1
  Duration        00:04:54
  Sql Severity    13
  Sql Message ID    1205
  Operator Emailed    
  Operator Net sent    
  Operator Paged    
  Retries Attempted    0

  Message
  Executed as user: mydomain\sqlsvc. Transaction (Process ID 77) was deadlocked on lock resources with another process and has
  been chosen as the deadlock victim. Rerun the transaction. [SQLSTATE 40001] (Error 1205). The step failed.

  Closest deadlock found in error log and extended events correspond to   1/16/2019 5:00:00 AM

  Question
   Why deadlock generated by sql agent job ( step executing stored procedure)  not detected error log and extended events ?