We are receiving "Max Connections has reached" error message while logging on to SQL Server database through applications. Then the application quits.
Server Config.: SQL 7 with SP7 on NT 4 with SP5. Workstations - Win 95 and 98. Default Client connectivity Protocol - TCP/IP and connecting through - ODBC.Note:
- We never set any connection limit on the SQL Server Properties.
- License configuration - Per Seat
- We have 70 client access licenses, but less than 50 users are using the application at a time.
- Once the user logs on to the application, SQL Server creates more than five connections for each user. Sometimes it exceeds more than 10. I can see this through current activity in the Enterprise Manager.
Shut down the license service and leave it shut down. This service has caused more problems in NT than it ever fixed and I have yet to find a company where it was accurate anyway.
For More Information
- Dozens more answers to tough SQL Server questions from Michael Hotek are available here.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- The Best SQL Web Links
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.