Domain.com uses SQL Server 2005. Users report with increasing frequency that they receive deadlock error messages in an order processing application. You need to monitor which objects and SQL Server session IDs are involved when deadlock conditions occur. You want information about each participant in the deadlock.

What should you do?

A.
Trace the Lock:Timeout event by using SQL Server Profiler.

B.
Observe the SQLServer:Locks – Number of Deadlocks/sec counter by using System Monitor.

C.
Trace the Lock:Deadlock event by using SQL Server Profiler.

D.
Trace the Lock:Deadlock Chain event by using SQL Server Profiler.

Explanation:
Use SQL Server Profiler to identify the cause of a deadlock. A deadlock occurs when there is a cyclic dependency between two or more threads, or processes, for some set of resources within SQL Server. Using SQL Server Profiler, you can create a trace that records, replays, and displays deadlock events for analysis.