View Full Version : Limit of MS Access
06-07-2007, 07:43 PM
Certainly this forum discuss ASP, however do you use a database together the ASP scripts?
I would like hearing from yours the limit in mb or records can have a MS Access database - no lost its performance.
5mb? 10mb? 50mb? more?
I am trying use large MS Access databases online.
06-07-2007, 09:15 PM
The biggest Access database I have ever worked on became just over 1GB offline in a Visual Basic app I created.
Online? I wouldn't take a chance on "big in size" database, Access is not the best at that, well in my years of working with them they haven't performed well unless they stayed under the 10MB mark!
I would suggest if I may that you use MS SQL or even PHP and MySQL.
Haven't done any benchmark tests on an Access database as my "code was right", that is the biggest part when working with databases;
Access, MS SQL or even MySQL your coding has to be right.
Hope the helps you.
06-07-2007, 11:24 PM
If you're working with large Access databases online, then I'd suggest that you migrate them over to SQL Server, if you can.
06-08-2007, 03:47 AM
I know the best solution in database for Win is MS SQL,but the major part of Hosting companies give a short disk space for it.
For example, the godaddy.com have an affordable Win Plan - 100gb of disk space,bas only 200mb for MSSQL, however it costs only 6,30 USD.
06-08-2007, 06:36 AM
the biggest issue with MS ccess databases is concurrent connections, e.g. more than 4 or 5 users and it will start to slow down... quickly, & not much more until it falls over, its probably the worst multi-user option there is.
06-08-2007, 06:52 AM
I would have to say that what you are saysing is incorrect - even though I didn't do any benchmark tests, I do remember that I had about 500 users a day accessing a website that was developed for Medical people, ontop of that I developed a database in Access for the Art awards in SA and we had about 3000 hits a day.
I am sure that, actually I know that Access can only really handle about 20 concurrent connections "by book terms", then you will see a tiny change in speed.
Remember it is your coding that is the speed changer!
06-08-2007, 07:18 AM
I appreciate your experience, I can only go by mine, perhaps for simple selects and nothing else you may get 20 concurrent users but any time you try to do writes you start (in my experience) to suffer as soon as you have more than 2 or 3 concurrent users.
I also noticed times when even though the system stayed alive data was corrupt in that referential integrity was sometimes ignored in multi-user situations, I did not try that hard to fix it since the alternatives are many and reliable.
06-08-2007, 07:26 AM
Fair enough, I guess it just depends on the way it is coded or written.
The objective behind coding properly is all to do with selecting the right data from the database, something I have had issues with in PHP as it is not my flavour as I coded for 8 years in ASP.
What do I mean?
If you only need the ID then select just the ID not the entire table and so on...
06-08-2007, 07:54 AM
I agree with you in that bad database design and poorly written SQL will slow & can eventually kill any DB.
The point is that mssql/MySQL.PostgreSQL/firebird/etc etc will handle far more concurrent users before it falls over regardless of the quality of the database deign.
Access I can't see getting even near the above even with optimized db and sql, its a great tool for many projects but again IME does not handle concurrency very well, even in small networks.
06-08-2007, 01:23 PM
I have also a website using MAAccess. My database have near 3mb and my website receives 400-700 visits per day. I donīt know if the access is fast or slow, but I am working with this database since 2001.
The best MS SQL disk space hosting is lunarpages.com - unlimited disk space -.
Powered by vBulletin® Version 4.2.2 Copyright © 2017 vBulletin Solutions, Inc. All rights reserved.