Hi
We have an ASP.NET web application running on Windows 2003 connecting to a
SQL Server 2000 database on the same machine, currently with 450 users,
approx 10-20 concurrent users. We use Windows Authentication for logging on
to the web application which is configured so that each user connects to the
database using their own NT user account. We have ASP.NET connection
pooling enabled and are aware that for each user connecting to the database
a new connection pool is created. Min pool size is set to 0, max pool size
is set to 100. We are finding it difficult to work out the maximum number
of connections (both total and concurrent) the system will allow in its
current state. Anyone any ideas?
We are also trying to come up with a quick short term solution to deal with
an increase in users in the near future as we are sure that the system is
nearing its current limit. Would changing the system to use one NT group
login into sql server be a preferred configuration? Would scaling up
hardware be the first step? Any other short term ideas would be greatly
recieved.
Regards
Steve A.
>> Stay informed about: Maximum Connections