Last post Aug 15, 2008 02:19 AM by Mikesdotnetting
Aug 14, 2008 11:57 AM|hkbeer|LINK
I have a ASP page with Gridview that updates the mdb file.
I put this page on web server to allow many user to edit & add the record.
Is there anything I need to be aware of for max number of concurrent user ?
What are the limits and how I can maximise the concurrent user to make sure smooth operation?
Thanks a lot for advice in advance.
Aug 14, 2008 03:18 PM|Mikesdotnetting|LINK
A "user" in the context of a web application is a live connection to the database. It exists for milliseconds, so long as you open the connection as late as possible, and close it as soon as you are done. Using a SqlDataSource control will manage this
for you. The actual limits for any particular app are impossible for anyone to predict. If the application begins to slow down, then it's time to think about moving to Sql Server. INSERTs and UPDATES are more demanding on the database that SELECTs, but
exactly how much more will differ from one scenario to the next. I have had Access database sites perform very well with 50 - 100,000 SELECTs a day.
Aug 14, 2008 06:25 PM|hkbeer|LINK
How to make sure it open late and close early ? What are the skiils ?
I fear some users would just edit the record and in the middle go for a coffee.
"Using a SqlDataSource control will manage this for you. "
So do you mean even my database file is Access, I 'd better use SqlDataSource Instead of AccessDataSource in VS2005/8 ?
Aug 15, 2008 02:19 AM|Mikesdotnetting|LINK
You can use the AccessDataSource control if you like, but I would use the SqlDataSource control:
Doesn't matter if a user never finishes updating a record. The connection to the database isn't open all the time. It is only open long enough to get the records for the page. The execution (much simplified) looks like this:
User requests page
Web server accepts request and passes it to ASP.NET to handle
ASP.NET sees that some data is needed and opens a connection to the database to get the records
The records are retrieved
The connection is closed
ASP.NET does something with the data (bind to GridView etc)
ASP.NET generates html showing the records on the page
Web server sends the html to the user's browser
ASP.NET doesn't care what the user does with the page. It has done all it needs to. It's no longer connected to the database, and is never connected to the user.