Multiple connection, helpppppp!
-
-
Can Someone show me any solutions to solve this problem? :confused::confused::confused: (When A planty of ppl try to connect to my database over asp.net page at the same time). I'm afraid my server will be "die" soon. :((:((:(( Thanks in-advanced!
-
Make sure that you close every Connection, DataAdapter and DataReader you use. --- b { font-weight: normal; }
Sorry, I dont mention about source-code problem (I think I wrote very well :-D). I really want to ask you is how many connection can connect to the database as the same time? (for ex: e-learning, there are alot of ppl login to a class at the same time. What will happen?) How do I solve this prob? If I use remoting technology, I can get an instant of Connection object from server. So that, I dont worry about the quantity users who connect to the database. But I dont use that tech! OMG! I hope you can understand what I say! My English isnot good! :(( Try to help me plz!
-
Sorry, I dont mention about source-code problem (I think I wrote very well :-D). I really want to ask you is how many connection can connect to the database as the same time? (for ex: e-learning, there are alot of ppl login to a class at the same time. What will happen?) How do I solve this prob? If I use remoting technology, I can get an instant of Connection object from server. So that, I dont worry about the quantity users who connect to the database. But I dont use that tech! OMG! I hope you can understand what I say! My English isnot good! :(( Try to help me plz!
That depends a lot on what kind of database you are using. Access database drivers can handle 64 concurrent connections. A real database server (for an example MySQL or MS SQL Server) can handle a lot more. As the duration of a connection to the database each time is only a few milliseconds, this means that you can have hundreds of visitors at the same time without running out of database connections. You can set a limit in the web server on how many threads will be used to process requests. If you set this number lower than the number of connections the database can handle, you will never ever run out of connections, assuming that each page only uses one connection at a time. --- b { font-weight: normal; }
-
That depends a lot on what kind of database you are using. Access database drivers can handle 64 concurrent connections. A real database server (for an example MySQL or MS SQL Server) can handle a lot more. As the duration of a connection to the database each time is only a few milliseconds, this means that you can have hundreds of visitors at the same time without running out of database connections. You can set a limit in the web server on how many threads will be used to process requests. If you set this number lower than the number of connections the database can handle, you will never ever run out of connections, assuming that each page only uses one connection at a time. --- b { font-weight: normal; }