LinkedIn | FaceBook | Twitter
This report shows information similar to the Locking and Blocking reports I’ve covered in the other posts in this series, but since this is a database-level report, it only focuses on one database at a time, and it gives you more lock information than some of the server-level reports.
The first band groups the blocking information by the Transaction ID, which is a unique number assigned to each unit of work the server is doing. You can use this number to locate lots of other information in many of the Dynamic Management Views or other Meta-Data views:
The second band starts a grouping for the Blocking SQL Statement.
The third band groups the information into Direct or Indirect blocks. A direct block results from a statement that blocks another, and an indirect block happens when one statement causes a cascading effect that eventually causes a lock. This is useful information you can use to track down the actual cause of the blocking behavior.
The last band groups its information by the Blocked SQL Statement. You’ll see the previous columns duplicated, which is useful in a blocking chain.
PingBack from http://geeklectures.info/2008/01/02/sql-server-management-studio-standard-reports-%e2%80%93-all-blocking-transactions-databasename/