Blocking in profiler?

Is tehre a way to profile blocking that occurs on a SQL Server?
Thx
Dedrick
There is a deadlock chain seet of events, but there is not a good and direct
way to watch the aggregate impact of blocking. You can see how long locks
take to acquire with the lock events, but these are typically too voluminous
to run on a productioin server. Alas, there is not data column for any of
the stmt completed events that will let you see the amount of time a
statement waited on locks.
However, dbcc sqlperf(waitstats) is a good source of this info. Combined
with sampling of sysprocesses and profiler data you can usually figure out
which statements are being blocked for significant periods of time
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
|||To add to Brian's response, you can monitor the Profiler Locks: Lock
Acquired event for long durations. Be sure to filter for a value > 0 since
the data can be quite voluminous.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick