June 13, 2013 at 8:45 am
Hello,
I have an application that connects to a SQL 2005 ENT Database. The app (running on a cluster like environment) on average runs 131 concurrent connections. I notice in the app logs the following error:
Maximum count of allowed ODBC sessions are exceeded. (Current: 4, Preferred: 3) (FILE: Main.cpp LINE: 840)
RELEASED the ODBC sessions exceeding the maximum amount. (Current: 4, Preferred: 3)
Our SQL Server connections are set to "0" unlimited. Does anyone know it there is a setting somewhere in SQL or ODBC where I can increase the sessions limit?
I've searched around and found something about pooling?
Thanks so much!
July 26, 2013 at 1:59 pm
bluefox (6/13/2013)
I have an application that connects to a SQL 2005 ENT Database. The app (running on a cluster like environment) on average runs 131 concurrent connections. I notice in the app logs the following error:Maximum count of allowed ODBC sessions are exceeded. (Current: 4, Preferred: 3) (FILE: Main.cpp LINE: 840)
RELEASED the ODBC sessions exceeding the maximum amount. (Current: 4, Preferred: 3)
Our SQL Server connections are set to "0" unlimited. Does anyone know it there is a setting somewhere in SQL or ODBC where I can increase the sessions limit?
Are the error messages on application log?
Is Apache involved?
If you got two "yes" answers this is an Apache issue, not a SQL Server one.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply