hi experts, My 2005 database is experiencing lots of transaction deadlocks. I want to run a Profiler Trace that will collect the Database Name, names of the stored procedures. And if possible the table name that was deadlocked. But the most important things are the SP names. Which events do I need to collect in my profiler trace? Thanks, John
Lots of stuff to read here:Troubleshooting deadlocks in SQL2005 Detecting and Ending Deadlocks How to Track Down Deadlocks Using SQL Server 2005 Profiler
for profiler deadlock events please check here http://www.extremeexperts.com/sql/Yukon/DeadLockDetection.aspx
Satya, I have far too many deadlocks to have to walk thru the logs manually. That's why I configured a Profiler Trace to write the information into a table that I can generate a report from. And yes the proc names are embedded in the huge deadlock graph's Text column but that also requires a manual review. Thanks to everyone who replied. John
John I agree it is not quicker way to find out, but in case the server is already hammered with deadlocks the performance will be dented when using PROFILER or any other monitoring tools to get the information. Anyway you need to go through the TSQL or stored procedure from that Text column and reduce the deadlocks.
If the server has been finalized and will weaken the performance of deadlock using Profiler or any other monitoring tools to obtain information.