January 24, 2014 at 8:54 am
Hi.
I have some cases here:
If I have 1000 concurrent users that log in to application and doing process that connects to SQL Server (insert, read, update, etc) at the same time, does that mean there will be 1000 user connections established in SQL Server? If not, how do i count the connection that established by application to SQL Server?
I need to see if the server memory is enough for the SQL Server.
Thanks for any explanation.
January 24, 2014 at 9:30 am
Not necessarily. If you have 1000 people connected to a web server, there could be 1000 connections from the web server to the database server, or there could be more, or (probably) less.
Web servers use connection pooling, so connections used by one user are recycled by other users. However, if your application does not close connections, they will build up, until the web server's connection pool is exhausted.
The best way to see if a database serve is adequate, is to run the application with the expected load (or more, if possible). Monitor the SQL Server to see if you have abnormally high CPU, disk queues, or low page life expectancy. Also watch the application to see how it is performing. Nothing says everything has to be a database server problem.
January 24, 2014 at 9:38 am
Let's say all 1000 user really connect at the same time, does any of them use recycled connections from other?
Is establishing connection to SQL Server consumes memory? How much?
January 24, 2014 at 9:42 am
Matt Crowley (1/24/2014)
Web servers use connection pooling, so connections used by one user are recycled by other users. However, if your application does not close connections, they will build up, until the web server's connection pool is exhausted.
Does SQL Server's connections use recycled connection too?
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply