December 31, 2008 at 3:36 am
Hi,
I am getting the following alert atleast once in a week.
Could you tell me how to trouble shoot this?
Name:
SQL Server User Connections > 500
SQLServer:General Statistics: User Connections: value = 503
Source Computer:
Regards,
Nagendra.
December 31, 2008 at 4:03 am
That is referring to the performance counter SQLServer:General Statistics: User Connections
There must be a threshold configured in MOM that is set to look for that being over 500. If that number seems too high for your environment then you should investigate where the connections are coming from by running sp_who2 on that server and look at the output. If that does not seem too high (which it is not in most environments) then I would consider raising the threshold.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
December 31, 2008 at 4:40 am
Hi,
Since i am SAP Basis Administrator and i am not aware how to configure and check these parameters, i need more help from you.
could you tell me more clearly how to troubleshoot this?
Shall i get any documentation for this?
Kindly help me.
Regards,
Nagendra.
December 31, 2008 at 5:01 am
I am totally unfamiliar with MOM outside of the general concept behind it so hopefully some others on this site can help. You might also want to check the MS forums associated with MOM to see if you can get any help there.
As to the area of SQL Server connections, you should definitely verify that the number of connections is something that is acceptable. Again, 500 doesn't seem high to me but I don't know what your environment is like. Run the sp_who2 command in a SQL Server Query Analyzer window and look through the results. That will show you who is connecting, with what application, etc.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
January 1, 2009 at 9:08 pm
I've had issue getting similar alert from MOM where there was more than 500 connections made to a database. Thinking there no way this many connection can be made to this instance (because we knew how many users we had), did a check and there were more than 500 connections made, and the culprit was MOM itself! Restarting MOM service resolved this issue but we had no idea why it happen, neither does Microsoft!
Simon Liew
Microsoft Certified Master: SQL Server 2008
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply