As @Hutch pointed out, one of the major limitations of `sp_who2` is that it does not take any parameters so you cannot sort or filter it by default.  You can [save the results into a temp table][temp sp_who2], but then the you have to declare all the types ahead of time (*and remember to `DROP TABLE`*).

Instead, you can just go directly to the source on `master.dbo.sysprocesses`

I've constructed this to output almost exactly the same thing that `sp_who2` generates, except that you can easily add `ORDER BY` and `WHERE` clauses to get meaningful output.



    SELECT  spid,
            sp.[status],
            loginame [Login],
            hostname, 
            blocked BlkBy,
            sd.name DBName, 
            cmd Command,
            cpu CPUTime,
            physical_io DiskIO,
            last_batch LastBatch,
            [program_name] ProgramName   
    FROM master.dbo.sysprocesses sp 
    JOIN master.dbo.sysdatabases sd ON sp.dbid = sd.dbid
    ORDER BY spid 

[temp sp_who2]: http://www.sqlmatters.com/Articles/sp_who2%20-%20filtering%20and%20sorting%20the%20results.aspx

How to get detailed list of connections to database in sql server 2005?