February 13, 2009 at 5:28 pm
hello,
We have a clustered instance sql server 2005 EE, which has sharepoint databases in it. We are also using Spotlight for monitoring. We are frequently getting an alarum saying that sql server is proceesing 52 logins for second. Then I started to analyze the SP_WHO2 output.In this out put I have couple of questions:(See the attachment)
1. Most of the logins STATUS is sleeping and LAST COMMAND is AWAITING COMMAND. What is this means?
2.Logins ABC\MOSSADMIN n ABC\spsearch are accessing the databases all the time 24/7 and status is sleeping.Why this 2 logins accessing all the time? can we do any thing to limit these logins from accessing?
3.I can see olny runnable login which is my login accessing quest database. How we will who are the users currently accesing the sql server databases?
Regards
Mani
February 13, 2009 at 8:24 pm
1. Most of the logins STATUS is sleeping and LAST COMMAND is AWAITING COMMAND. What is this means?
These indicate that the are not running while you executed sp_who2.
2.Logins ABC\MOSSADMIN n ABC\spsearch are accessing the databases all the time 24/7 and status is sleeping.Why this 2 logins accessing all the time? can we do any thing to limit these logins from accessing?
You need to make sure whether or not these accounts may do something sporadically. If they are only connections and do nothing, you can write a script to check its idle time. When idle time is greater than your expected period, these connection will be killed.
3.I can see olny runnable login which is my login accessing quest database. How we will who are the users currently accesing the sql server databases?
You can find the hostname where a user starts his/her tasks by using sp_who2. You may find the information on the user in your activity monitor or by running SELECT * FROM sys.sysprocesses.
Hopefully, I answered your question rather waste your time.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply