webpages and access db

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have done some reading and heard comments on ms access and webpages in
regards to how ms access limits 10 concurrent connections.

So i tested it like this - a asp webpage with information coming out of a ms
access 2003 db and on a computer i open 66 instances of that page and they
all worked. Comments....
 
Alex: I went through this years ago with an e-commerce site I built. I
heard all the comments about 10 simultaneous connections.

I did a lot of reasearch. And, I monitored the activity.

It is my understanding the *true* number is about 255 *if* you don't have a
lot of activity at once.

--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
===
|I have done some reading and heard comments on ms access and webpages in
| regards to how ms access limits 10 concurrent connections.
|
| So i tested it like this - a asp webpage with information coming out of a
ms
| access 2003 db and on a computer i open 66 instances of that page and they
| all worked. Comments....
 
i notice just a few seconds delay with the other pages. So i guess that myth
is dead folks.
 
Access can handle 6000 users/hour, if the site is well coded and on a well hosted IIS web server.

For me, "well coded" means that I open and close tables immediately after use, but not the actually
database connection.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
But did you try it from 66 different computers??

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
no did it on the same computer and opened it up in 66 different i.e.
instances which i figure to equal concurrent connections. which maybe wrong,
don't know....but check what the others have said which tells me the limit is
much higher than 10.
 
The 10 concurrent connections is not something I've seen as a hard-limit.
Instead it's more of a guide. It's long been known that Access tends to
break down with numerous concurrent users. For a lot of people, this is
somewhere over 10, but not too far over. The behavior doesn't show itself as
much if you are using SELECT statements for the most part. It's when you
start to do a lot of Insert/Updates that things really get bad. This is
where Acces really begins to degrade with a low level of activity.
Connection pooling in ADO helps that out. Opening 66 instances of the page
isn't a good metric because that does not constitute 66 simultaneous
connections because, once the page is served to the browser the browser is
no longer connected. You would need a load analyzer tool that launches
multiple TCP/IP connections to the site for page requests in order to get a
true idea, and chances are the Windows limit of 10 connections (for
non-server OSes) would be hit first. That may be where a lot of users get
the idea that it is hard-coded to 10 connections. The non-server OSes are
limited to 10 simultaneous connections and not necessarily Access.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
 
Back
Top