![]() You are aware that sql_text won't show up for lock_deadlock_chain? The only informations you can get in sql_text is the one of the process which got killed. Then this: "With both events selected, click on the configure button, and a new window will appear, in this window we will capture the sql_text field to be able to see the query that caused the deadlock". What does the transaction_id and session_id does for us? It doesn't give any pertinent details. Help a bit to understand the Extended Events but the end result is not so good. the information (more or less) you need to collect is up to you. The objective of this tip is to show which events we should capture for deadlocks. This is a basic guide, and the output is a simple SELECT query, so you can add/remove columns you need, you can freely remove the columns you don't need. Wednesday, Ma2:57:06 PM - Eduardo Pivaral I think the pre-installed session already contains deadlock events - doesn't it? In session 1 run this query (use any test table you want): In this example, we are updating the same record on each table for each Testing SQL Server Extended Events with a DeadlockĬreating a deadlock for testing purposes is very simple, all you need is 2 Now our event to capture deadlocks is created, it is just a matter of testing SECONDS,MAX_EVENT_SIZE=0 KB,MEMORY_PARTITION_MODE=NONE,TRACK_CAUSALITY=OFF,STARTUP_STATE=ON) WITH (MAX_MEMORY=4096 KB,EVENT_RETENTION_MODE=ALLOW_SINGLE_EVENT_LOSS,MAX_DISPATCH_LATENCY=30 ![]() The event session advanced parameters, you can see that the event starts automatically Events to track Lock_deadlock and Lock_deadlock_chainĪDD TARGET package0.event_file(SET filename=N'deadlock_capture')
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |