Grab a pen and notepad, and jot down your answers as you go, then check your answers at the key at the bottom of the page.
Questions
Q1. What does a deadlock graph NOT contain?
- Inputbuffer for the sessions involved
- Locks requested by the sessions involved
- Locks obtained by the sessions involved
- Execution plans for the sessions involved
Q2. Why not just pick up deadlock information from the System Health Extended Events session?
- The System Health session is only available in SQL Server v.Next
- Data in the System Health session doesn’t persist after restart
- The System Health session requires that you use Profiler to read it
- The System Health session never picks up deadlocks
Q3 Why does the index in the video prevent the deadlock from happening?
- The index was created with NOLOCK
- Update statements can only ever lock one index at a time
- Update statements can only ever lock the Clustered Index of a table
- The new index doesn’t contain the LatestRecordedPopulation column
Scroll down for the answer key :point_down:
Answer Key
- A1. 4. Execution plans for the sessions involved.
- A2. 2. Data in the System Health session doesn’t persist after restart
- A3. 4. The new index doesn’t contain the LatestRecordedPopulation column.