|
Home > Archive > FrontPage Server Extensions for Windows > October 2004 > Limit on # of Access connections?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Limit on # of Access connections?
|
|
|
| Based on a recommendation by several people here, I am
going to setup an Access database to store
usernames/passwords of a subweb that I am going to
password-protect through ASP pages and that database
(instead of using FrontPage Permissions).
This particular web site has hundreds of users. Is there a
limit to the number of records an Access database will be
able to successfully handle? And is there a limit on the #
of simultaneous database connections? Before I create the
database and recode these pages for the login script, I
want to make sure it'll be able to handle the high number
of users.
| |
| Mark Fitzpatrick 2004-10-15, 9:11 pm |
| Access has a limit to the number of records in a table, but it's in the
millions of records. The real problem is the number of simultaneous
connections that Access supports. Access tends to really degrade with about
10 to 15 simultaneous connections. There are lots of things that affect this
though. A simple select against an Access database isn't as bad as an
update/insert/delete so more selects can be run at a time than anything.
Hitting a login page will probably be a minimal drain on the site since all
you're doing is requesting validation once. If you have a lot of data-driven
pages behind though that are pulling content based on a user's preferences,
you may have to look at various ways to cache some of the data to make it
more efficient.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
"Kelly" <anonymous@discussions.microsoft.com> wrote in message
news:1f8a01c4afb3$fe1bfb70$a501280a@phx.gbl...
> Based on a recommendation by several people here, I am
> going to setup an Access database to store
> usernames/passwords of a subweb that I am going to
> password-protect through ASP pages and that database
> (instead of using FrontPage Permissions).
>
> This particular web site has hundreds of users. Is there a
> limit to the number of records an Access database will be
> able to successfully handle? And is there a limit on the #
> of simultaneous database connections? Before I create the
> database and recode these pages for the login script, I
> want to make sure it'll be able to handle the high number
> of users.
|
|
|
|
|