September 12, 2011 at 2:20 am
HI all,
I added a perfmon counter for no of user connection to sql :
SQL Server General statistics : User connections
Its showing arround 200 connections :
I have a question ?? what are the max no of user connections allowed by a SQl server . ??
Regards,
Lavanya
September 12, 2011 at 2:58 am
The maximum number of connections is 32,767 (you can check it out at http://msdn.microsoft.com/en-us/library/ms143432(v=SQL.90).aspx"> http://msdn.microsoft.com/en-us/library/ms143432(v=SQL.90).aspx). Of course this is a theoretical issue. I’ve never had a server that had even 10% from that number.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
September 12, 2011 at 3:41 am
You can also execute following command:
SELECT @@MAX_CONNECTIONS
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
September 12, 2011 at 4:32 am
Hi friend,
Thanks for the quick response and thanks for the information .
this is the correct way to check the user connections ???
SQL Server General statistics : User connections
September 12, 2011 at 6:17 am
Lavanyasri (9/12/2011)
Hi friend,Thanks for the quick response and thanks for the information .
this is the correct way to check the user connections ???
SQL Server General statistics : User connections
If you want to check how many active connections SQL Server is serving in a particular moment, you can run this query:
select count(*)
from sys.dm_exec_connections
If you want to see how that number changes in time, the perfmon counter would do.
-- Gianluca Sartori
September 13, 2011 at 2:12 am
this should do you good. Lists only active users.
USE msdb
SELECT * FROM sys.dm_exec_sessions WHERE Status != 'sleeping'
This shall probably give you a better idea to whom to keep and whom to kick out if there is a bottleneck.
USE msdb
SELECT * FROM sys.dm_exec_sessions
September 15, 2011 at 9:50 am
Adi Cohn-120898 (9/12/2011)
The maximum number of connections is 32,767 (you can check it out at http://msdn.microsoft.com/en-us/library/ms143432(v=SQL.90).aspx"> http://msdn.microsoft.com/en-us/library/ms143432(v=SQL.90).aspx). Of course this is a theoretical issue. I’ve never had a server that had even 10% from that number.Adi
I've hit this limit... I have around 200 application servers that have around 12000 connections total if everything is normal. If all DB sessions on the application server are in use (blocking) for some reason, it will add connections, so if I have a DB hiccup, perhaps a table lock on a very busy table, the application servers start adding connections. A crash issue with SQL Server 2008 made me unable to release idle connections, as doing so increased the frequency of crashes quite a lot. I've only hit the limit when I've had issues though...
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply