I've now released a successor to my aba_lockinfo, named beta_lockinfo. The
main reason there is a new name, so that you (and me!) can run both in
parallel, as beta_lockinfo certainly is a beta at this point.
beta_lockinfo is more or less a complete rewrite of aba_lockinfo,
necessitated by the introdction of the DMVs and the catalog views in
SQL 2005. I've taken the oppurtunity to review the parameter list, and
the there is a change to the default output format, so that process
information is printed on the first only. As for what data that is
exposed, there is a lot more to choose from in the DMVs, but I've picked
what I think make sense.
beta_lockinfo reqiures SQL 2005 SP2, as I some columns and DMV that was
added in SP2.
You find it on http://www.sommarskog.se/sqlutil/beta_lockinfo.html.
For those who don't know what aba_lockinfo, and thus beta_lockinfo, is,
I should say that it is a stored procedures that compiles information
about processes and locks, and displays the blocking chain, so that you
can quickly kill the blocker, yet have information so that you can analyse
how the situation arose.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se
Books Online for SQL Server 2005 at
Books Online for SQL Server 2000 at
main reason there is a new name, so that you (and me!) can run both in
parallel, as beta_lockinfo certainly is a beta at this point.
beta_lockinfo is more or less a complete rewrite of aba_lockinfo,
necessitated by the introdction of the DMVs and the catalog views in
SQL 2005. I've taken the oppurtunity to review the parameter list, and
the there is a change to the default output format, so that process
information is printed on the first only. As for what data that is
exposed, there is a lot more to choose from in the DMVs, but I've picked
what I think make sense.
beta_lockinfo reqiures SQL 2005 SP2, as I some columns and DMV that was
added in SP2.
You find it on http://www.sommarskog.se/sqlutil/beta_lockinfo.html.
For those who don't know what aba_lockinfo, and thus beta_lockinfo, is,
I should say that it is a stored procedures that compiles information
about processes and locks, and displays the blocking chain, so that you
can quickly kill the blocker, yet have information so that you can analyse
how the situation arose.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se
Books Online for SQL Server 2005 at
Books Online for SQL Server 2000 at