Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-02-24 : 07:37:25
|
| murthy writes "what are things i will get to know using sp_who system stored procedure. Why one should use this procedure." |
|
|
Sarat
Constraint Violating Yak Guru
265 Posts |
Posted - 2003-02-24 : 11:14:30
|
| murthy,sp_who provides information about current Microsoft SQL Server users and processes. You can view the same info via Current Activity window in EM also.sp_who provides info like spid, ecid,status,loginame, hostname, dbname , cmd etc. you can find the what each means under help.thanks,sarat. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-24 : 16:26:37
|
| Well you should use sp_who instead of looking at the Current Activity window in EM. Bringing up the Current Activity window can cause the server to be sluggish if there is a lot of activity occurring in SQL Server. Also, use sp_who2 for additional information. |
|
|
|
boligoma
Starting Member
5 Posts |
Posted - 2003-02-26 : 18:27:20
|
| For me, it also works a query to master.dbo.sysprocesses table. I used it mainly to see the I/O buffers each process use,to see if one process block another one an why, and who is running which process into the SQL Server.It's like viewing the current activity in the EM and to see other information that in the sp_who doesn't show. |
|
|
|
|
|
|
sp_who