Open connections from web to dbase in asp.net
-
Hello, I have a small question. i have read that normally you should only have 1 connection open to the dbase and not a second one , or at least there has to be a good reason why the second one is open. i am develloping an application that everytime a user enters in his account opens and closes a connection, it does so for all the users that login in their account so if there where 4000 users it would open 4000 connections and miliseconds later close them again. should this be changed to an other process from wich the dbase is stored in memory? who can tell me? the application involves a lot of user loggin in constantly roberto lorusso
-
Hello, I have a small question. i have read that normally you should only have 1 connection open to the dbase and not a second one , or at least there has to be a good reason why the second one is open. i am develloping an application that everytime a user enters in his account opens and closes a connection, it does so for all the users that login in their account so if there where 4000 users it would open 4000 connections and miliseconds later close them again. should this be changed to an other process from wich the dbase is stored in memory? who can tell me? the application involves a lot of user loggin in constantly roberto lorusso
rlorusso wrote:
i have read that normally you should only have 1 connection open to the dbase and not a second one
Either the recommendation is written for applications that themselves doesn't handle multiple users, or it's implied that it's one connection per request. It's just because the application should be able to handle many requests that you should keep the number of connections per request as low as possible. --- b { font-weight: normal; }