What's the best way to monitor SQL Server Conccurency issues?
Specifically my goal is to reduce or prevent deadlocks and blocking and to catch potential concerns before they become a problem.

For example if I were to monitor windows performance counters for memory usage, I would be able to predict when memory issues would become a problem. I'm looking for a similar approach that monitors concurrency problems.

Thanks for your answer Nick! I was hoping for a metric that could catch potential trouble before they become a problem. If I'm catching deadlock graphs, it's too late to prevent them. The blocked process might be promising with a low enough threshold, but in terms of a measure or a performance indicator, the best I could do is count them. I know there are wait statistics, but I wonder how useful these are...
–
Michael J SwartJul 23 '10 at 14:56