InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 13:55:30 GMT20http://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxNice script.Tue, 04 May 2010 18:28:36 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxHi,Thank you very much for your comments and your suggestion.The stored procedure returns the HostName. Although it would be a simple exercise to get the IP address for the given HostName, it is beyond the scope of this stored procedure. I intended for the output to be in a familiar form for the DBA, as returned by sp_who2.The main use for this stored procedure is as a very fast tool to get the top processes using I/O resources.Thanks,MirceaSat, 17 Apr 2010 19:51:50 GMTMirceahttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxYes, your sp_who3 returns the same info as sp_who2 using the login param. I see. You retained existing code for this param while adding your own for the DB param.KenFri, 16 Apr 2010 08:29:09 GMTken.trockhttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxHi,Thank you for using the script and posting the comments. Could you please use the same login parameter in sp_who2 and compare the output ?You should get the same results as the ones you get in sp_who3.The main use for sp_who3 resides in it's ability to display all users for a certain database or set of databases.ThanksThu, 15 Apr 2010 21:55:09 GMTMirceahttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxI can get it to compile on SQL 2005 and 2008 on a couple IA64's and it runs ok using the DB param. If there's no DB matching the name it shows all processes. The Login name is a different story. I can get "<login> is not a valid login or you do not have permission." even when I'm looking for a legitimate login.Thanks,KenThu, 15 Apr 2010 14:10:40 GMTken.trockhttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxWorks nice in SQL Server 2008 x64! It would be better if you add the IP info!Thanks for sharing :cool:Thu, 15 Apr 2010 02:26:59 GMTDugihttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxHi,It appears that the TAB character was replaced by a series of 4 question marks (????) in the script I submitted.I will contact SQL Server Central and this will be corrected shortly.Thank youTue, 06 Apr 2010 18:23:04 GMTMirceahttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxcan't compile this proc on SQL Server 2005 SP2, x64get error:Msg 102, Level 15, State 1, Procedure sp_who3, Line 49Incorrect syntax near ' '.Msg 102, Level 15, State 1, Procedure sp_who3, Line 103Incorrect syntax near ' '.Msg 102, Level 15, State 1, Procedure sp_who3, Line 105Incorrect syntax near ' '.Msg 102, Level 15, State 1, Procedure sp_who3, Line 117Incorrect syntax near ' '.Msg 102, Level 15, State 1, Procedure sp_who3, Line 229Incorrect syntax near ' '.Tue, 06 Apr 2010 08:56:26 GMTboris_shvartsmanhttp://www.sqlservercentral.com/Forums/Topic895429-2662-1.aspxComments posted to this topic are about the item [b][url=/scripts/sp_who3/69906/]DBA Tools: sp_who3[/url][/b]Hi All,Just a note to let you know that the issue with the TAB characters has been resolved, so you can just copy and paste the script if you would like to use it.ThanksThu, 01 Apr 2010 19:22:33 GMTMircea