You administer a Microsoft SQL Server database named Orders.
Users report that during peak usage periods, certain operations are taking more time than expected. Your initial analysis suggests that blocking is the cause.
You need to gather more data to be able to determine which processes are being blocked and to identify the root cause.
What should you do?
A . Schedule a SQL Agent job to run every 60 seconds and insert the results of executing the sys.dm_os_wait_stats DMV into a table.
B . Use System Monitor to catch the Lock Waits/sec event
C . Use sp_configure to set the blocked process threshold. Start a trace using SQL Server Profiler to catch the Blocked Process Report event.
D . Start a Trace using SQL Server Profiler to catch the Lock: Deadlock event
Answer: C
Explanation:
The Lock: Deadlock event class is produced when an attempt to acquire a lock is canceled because the attempt was part of a deadlock and was chosen as the deadlock victim.
Use the Lock: Deadlock event class to monitor when deadlocks occur and which objects are involved. You can use this information to determine if deadlocks are significantly affecting the performance of your application. You can then examine the application code to determine if you can make changes to minimize deadlocks.
References: https://docs.microsoft.com/en-us/sql/relational-databases/event-classes/lockdeadlock-event-class