Comments posted to this topic are about the item <A HREF="/scripts/sp_who2/72823/">Capture and Alert for Blocked SPIDS with SP_WHO2</A>
Very good effort and nice script !
Just to add my 2 cents,
It is not good to run the job every 2 mins (or any interval) on a highly busy prod server as it has its own overhead.
I had this type of job running and emailing the blocking details, but have switched to EVENT_Notification
which uses BLOCKED_PROCESS_REPORT. This is smart enough to fire when there is real blocking (and this can be adjusted using sp_configure). This can fire a sql agent job to insert the xml generated by BLOCKED_PROCESS_REPORT into a db table and if you want more fancy reports, you can email it by shredding the xml.
If you want to do it that way... You can check out this article on it http://www.sqlservercentral.com/articles/Blocking/64474/
The way I did it was originally for a database used by a third party software that tends to have a lot of blocking that locks up the entire system.
We don't have access to the code to fix where the real problem exists.
I also include non-SQL people in the alerts and the details so they can share that information with the vendor... I even included a stored procedure for them so they can kill the blocking process in their database if the DBA is unavailable.
If your system can't handle running this every 2 minutes... you desperately need new hardware.
The entire process completes before I can take my finger off the mouse after clicking execute. (Registers 0 time and runs so fast it doesn't even register a blip on the processor/memory)
The only reason I put it as long as 2 minutes is that I know if I get two emails in a row it's an issue.