TSQL for capture and insert to a user table when blcoking is happening on a SQL server

Question

Hi,
I am searching for a TSQL which will capture the blocking script to a table with execution plan and all other necessaryu details. I tried with below script but its not giving the text for blocked statement
I t will be nice if i get RequestingText and  BlockingTest
SELECT @@servername as Instancename,getdate() as [date],session_id,start_time,status,command,database_id,blocking_session_id,
wait_type,wait_time,last_wait_type,ST.TEXT AS SQL,
wait_resource,open_transaction_count,cpu_time,total_elapsed_time,reads,writes,logical_reads,text_size from sys.dm_exec_requests SR
CROSS APPLY SYS.DM_EXEC_SQL_TEXT(SR.SQL_HANDLE) AS ST 
where blocking_session_id >0
I tried the below link also, this this script also got blocked
http://blog.sqlauthority.com/2010/10/06/sql-server-quickest-way-to-identify-blocking-query-and-resolution-dirty-solution/

Answer 1

But when you run select * from sys.sysprocesses where blocked >0 
i can see blocking
and it will be nice if I get RequestingText and BlockingTest
in the user table
You can get the requesting text for the spid that is blocked, plus all the other information you get from sys.sysprocesses by
select SUBSTRING(st1.text, (p.stmt_start/2)+1,
((CASE p.stmt_end
WHEN -1 THEN DATALENGTH(st1.text)
ELSE p.stmt_end
END - p.stmt_start)/2) + 1) AS RequestingText,
p.*
from sys.sysprocesses p
CROSS APPLY sys.dm_exec_sql_text(p.sql_handle) AS st1
where p.blocked <> 0;
But you will not bee able to get the command that caused the lock that is causing the blocking.  SQL does not keep that information.  For a lock, it only keeps the spid that owns it, what is locked, and the kind of lock.  It does not keep
the command that caused the lock.  And while you can, at least sometimes get the last command the blocking spid has issued, but that may well not be the command that caused the lock.  The command that caused the lock might be anything the blocking
spid ran since it entered transaction state.  And since that could be the last command or many, many commands ago, you won't be able to get that information with a query into the system tables and/or views.
Tom