What should you do to monitor which objects and SQL Server session IDs are involved when deadlock conditions occur?

You are employed as a database administrator at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. The Domain.com network contains a SQL Server 2005 database server named Certkiller -DB03.
You have received a report from the Domain.com users 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 also want information about each participant in the deadlock.
What should you do?

You are employed as a database administrator at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. The Domain.com network contains a SQL Server 2005 database server named Certkiller -DB03.

You have received a report from the Domain.com users 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 also want information about each participant in the deadlock.
What should you do?

A.
On Certkiller -DB03, use the SQL Server Profile and trace the Lock:Timeout event.

B.
On Certkiller -DB03, use the System Monitor and observe the SQLServer:Locks – Number of Deadlocks/sec counter.

C.
On Certkiller -DB03, use the SQL Server Profile and trace the Lock:Deadlock event.

D.
On Certkiller -DB03, use the SQL Server Profile and trace the Lock:Deadlock Chain event.

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.



Leave a Reply 0

Your email address will not be published. Required fields are marked *