Access database connections limit
Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: Database Discussion
Forum Description: Discussion and chat on database related topics.
URL: https://forums.webwiz.net/forum_posts.asp?TID=10596
Printed Date: 30 March 2026 at 12:09pm
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: Access database connections limit
Posted By: WebWiz-Bruce
Subject: Access database connections limit
Date Posted: 25 May 2004 at 5:51am
I've had an email sent to me with the following:-
I've always been lead to believe from what I have read on MSDN that Access can handle 255 simultanious connections per database. Can anyone confrim that the above is correct? ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
The Microsoft drivers provided currenly for Access only allow 64 concurrent
connections on a per-server basis, as such, you can experience timeout problems
in your script if you are on a shared server with other customers who use Access
heavily also, as the server will be sharing the 64 connections as a whole.Replies:
Posted By: zaboss
Date Posted: 25 May 2004 at 6:00am
|
Definitively wrong. There is no way it could be 64 conections per server. Any regular server host hundreds of site, be it even 100, but most are somewhere arround 300. Should each of them use an Access db, and even if each site has only one visitor, there are many chances that you'dd have 100 visitors on the server at a given time, which makes impossible to connect according to what you say, which obviously is not true. ------------- Cristian Banu http://www.soft4web.ro - Soft 4 web |
Posted By: dpyers
Date Posted: 25 May 2004 at 1:30pm
|
-Borg- Don't know what context the statement was made it, but they may be talking about connections through an Access/Jet application on a LAN, which, I believe, are less than 255. Term "connections" is misleading. I't doesn't mean what zaboss thinks it does. A concurrent connection can be thought of as a specific low-level data base activity - e.g. a read, a write - not as the connection you open in your script to a db. MSDE (SQL200 Desktop) for example supports 5 concurrent connections. Which means it can support a couple of hundred users. Because of the way MS SQL2000 handles it's low-level activity compared to Access's Jet DB Engine, you can support more users with MSDE's 5 connections than with Jet's 64/255. ------------- 
Lead me not into temptation... I know the short cut, follow me. |