sp_who v. sp_who2
-
This works sp_who 'keough', (it gives me only my SPIDs). This, sp_who2 'keough' gives me all SPIDs. This is undocumented, so a quick search indicated to me that sp_who2 'keough' should work the same.
Anyone had this problem or know what I am doing wrong?
TIA.
I wasn't born stupid - I had to study.
-
Doesn't work for me either ........ Looks like a bug in sp_who2.
-
Yes, definitely a bug in sp_who2. You can do
EXEC sp_who2 '55'to filter the output so you get only activity for spid 55, but not filter on the login name. The following comment from sp_who2 (near the end) explains why:/*****AKUNDONE: removed from where-clause in above EXEC sqlstr
sid >= ' + @charsidlow + '
and sid <= ' + @charsidhigh + '
and
**************/
But clearly then the proc does not work as (un)documented.
-
I have found this to be very useful, when dealing with over 300 connections:
sp_who2 'active'
...gives a list of active connections, ones where activity is not 'AWAITING COMMAND'
Dylan Peters
SQL Server DBA -
You can use sp_who2 as a template & make your own. I made sp_who2db to sort by database, and sp_who2lock which basically runs sp_who2 and sp_lock together
-
Check out sp_who1: http://www.windowsitpro.com/Article/ArticleID/45034/45034.html
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply