http://blogs.msdn.com/slavao/archive/2006/11/14/sqlosdmv-s-continue.aspxsys.dm_os_waiting_tasks One can run lots of interesting queries using this view. You can even use this view to perform deadlock detection that is not resolvable by deadlock monitor, DM. For example if you have tasks waiting on external resources suchen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/slavao/archive/2006/11/14/sqlosdmv-s-continue.aspx#1104763Mon, 20 Nov 2006 00:00:17 GMT91d46819-8472-40ad-a661-2c78acb4018c:1104763Mario Broodbakker<p>Slava, you provide great information not provided anywhere else, I love your blog, and I'm eager to see what else you want to share around dmv's: especially the wait stuff.</p> <p>What I terribly miss in SQLserver is wait information accumulated per session, and the possibility of wait information being traced. &nbsp;Like this view, it shows only present waiting sessions, but there is no history, you cannot distinguish the (waitable) resource consuming sessions from 'well behaving' ones. Unless you take very frequent samples which can be a costly thing to do on busy systems.</p> <p>When will SqlServer take that next step and collect that waitinfo per session or batch (sqlserver seems to collect other info per batch also..)?</p> <p>good luck!</p> <p>Mario</p>