Quantcast
Channel: SQL Server Database Engine Forum
Viewing all articles
Browse latest Browse all 15872

Event ID 17884 &1205 - Deadlock events not getting generated on Application log of Event viewer though Trace Flag set has deadlocks captured

$
0
0

Hello,

MSSQL 2016: Potential deadlocks exist on all schedulers on Node - This alert will get triggered when Event ID – 17884 is logged in the Application
MSSQL 2016: Transaction was deadlocked on resources with another process and has been chosen as the deadlock victim – This alert will get triggered when Event ID – 1205 is logged in the Application.

Above 2 Events are enabled by monitoring team ideally on the SCCM layer to alert whenever the Event ID gets recorded on event viewer. 

On SQL instance level we have Trace flag 1222 and 1204 set and SQL error logs contain the dumps generated on deadlock event.

Is my assumption wrong if  on the  above dumps generated i.e when SQL server errorlog captures the deadlock information the application event log gets the Event ID 17884 and Event ID 1205 , because currently we have sql errorlog capturing the deadlock but these event ID are not getting generated on the application log .

What has to be done on the DB server for these Event ID 17884 and Event ID 1205 to get generated on application windows log are they totally different from the information captured by deadlock trace flags set and captured on SQL server error log ?

Thanks

Eben


Viewing all articles
Browse latest Browse all 15872

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>