Syntax

sp_blocked_process_report_viewer [@Source = ] 'SourceOfTraceOrSessionTarget' [ , [ @Type = ] 'BPRFormat' ] 

Arguments
[@Trace = ] ‘SourceOfTraceOrSessionTarget’

If the blocked process reports you'd like to examine came from a trace file, then this parameter specifies the name of the trace table or trace file that holds the blocked process reports. 

If the blocked process reports you'd like to examine are in an extended events session, then this parameter specifies the name of the session (not the session target).

If you are using extended events as a source, the target must either be a ring_buffer or an event_file.

[@Trace = ] ‘BPRFormat’

Is the type of file referenced by SourceOfTraceOrSessionTarget. Values can be TABLE, FILE, XMLFILE or XESESSION. The default is FILE

 

Remember: When it comes to concurrency problems, you don’t have to guess what’s wrong!!!

I explain when to use this tool flowchart style!


You can see a "clickable" version of this flowchart at Michael J. Swart's blog at http://michaeljswart.com/2011/05/when-to-use-blocked-processes-reports/

Last edited Feb 23, 2016 at 9:15 PM by mjswart, version 7

Comments

mjswart Feb 23, 2016 at 9:20 PM 
Extended event ring buffers can now be used.
When setting up a trace, the most important columns to collect are "EndTime" and "TextData" for the "Blocked process report" event (under the category "Errors and Warnings"

JasonBcraig Oct 3, 2013 at 3:04 PM 
Can this report be used with extended event ring buffers or only sql profiler trace file / tables?

samgreene Dec 27, 2011 at 11:24 PM 
Anything special that needs to be captured in the trace?

I have a feeling I know that there is, but it would be nice to be documented here.