Exam 70-764 topic 1 question 146 discussion

Actual exam question from Microsoft's 70-764

Question #: 146
Topic #: 1

You are troubleshooting an application that runs a query. The application frequently causes deadlocks. You need to identify which transaction causes the deadlock.
What should you do? More than one answer choice may achieve the goal. Select the BEST answer.

A. Query the sys.dm_exec_requests dynamic management view.
B. Create a trace in SQL Server Profiler that contains the Deadlock graph event.
C. Query the sys.dm_exec_sessions dynamic management view.
D. Create an extended events session to capture deadlock information.

Show Suggested Answer

Suggested Answer: D 🗳️
Troubleshooting deadlocks -
You have been receiving reports from users indicating that certain applications are returning deadlock errors. To maximize the effectiveness of troubleshooting these problems, you decide to focus on the deadlocks that are hit most frequently. You create an Extended Events session that:
✑ Configures deadlock event tracking for the session.
✑ Specifies a target that aggregates based on an identifier for the deadlock.
You run the Extended Events session, and after additional deadlocks are reported you are able to obtain aggregated deadlock information, along with the complete XML deadlock graph for each source. Using this information, you are able to pin point the most common deadlocks and start working on a solution.

by TheSwedishGuy at Jan. 29, 2020, 12:08 p.m.

Comments

Submit Cancel

norbert1

4 years, 9 months ago

i dont get it - the correct answer for deadlock information hast been "use Profiler" - just happened in a recent question without someone saying NO.. so when to use profiler and when extendet event..?? someone knows..?

upvoted 1 times

Cococo

4 years, 8 months ago

Both Profiler and XE can do this but the question is - "Select the BEST answer." and XE is the best answer as Microsoft is going to deprecate the Profiler in the future

upvoted 1 times

...

TheSwedishGuy

5 years, 4 months ago

Just let an extended events session run in the background so as to capture any deadlocks that occur on random times.

upvoted 2 times

...