I am creating a solid application, with a SQL Server DB engine. I think my site will be accessed by thousands of users per second, depending on how many connections are there? How many connections can IIS hold, and SQL Server?
First of all, there is a difference between connection and connection pool. Is it good to look at it, because it makes a big difference in performance if you need a reference, then I can dig one, but google / bing is your friend here. Take the key: keep the number of connections pool at least
In addition, the number of connections depends on two things.
-
Are you using Windows Ath? If so, then each specific user will cause a different connection / connection pool
-
If you are using SQL AUTH, then each new connection string causes a new pool (Even a single space difference will be the cause of a new pool.)
Regarding the scaling question, both IIS and SQL Server can handle the number of connections Are there. If you are running in connection boundaries, then you should probably keep an eye on the app design.
Eric
Comments
Post a Comment