Comments on: A Better sp_who2 using DMVs (sp_who3)

By: Edward Pinto

Edward Pinto — Wed, 07 Mar 2012 18:51:56 +0000

This worked like a Charm Derek.. I was able to pinpoint the offender really quick and nip it in the bud.

By: Derek Dieter

Derek Dieter — Fri, 09 Sep 2011 17:03:24 +0000

Hi Peter,

This is because this script only shows active connections. Personally I prefer this because when troubleshooting, I can immediately see how busy the server is just by the sheer number of results. sp_who2 will show all connections and I need to figure out which ones are asleep. To change this to show sleeping connections, simply join the sessions table first, then left join on the dm_exec_requests

Derek

By: Sean

Sean — Mon, 11 Jul 2011 20:35:41 +0000

This script/sp rocks!

Thanks!

By: Peter

Peter — Fri, 10 Jun 2011 08:29:21 +0000

Nice work but it only seems to find connections to the master,tempdb databases…

EXEC SP_WHO2 gives me about 100 result and your query only 20…

By: Steve

Steve — Fri, 27 May 2011 13:41:16 +0000

I see now the who3 CPUTime figure is coming from the first who2 row of 7 parallel processes for my query, which is done (or not changing) in who2.