Access has a limitation on the number of concurrent users and as such isn't intended or designed for high-volume, multi-user use.
Microsoft have previously said that they "recommend that Microsoft Access be used solely for development purposes and not for production" so if you are going to be using the database for anything other a local data store for yourself, I'd suggest going with another database.
As has been said, SQL Server comes in a few varieties, one of which is the free Express edition:
>> access databases with many millions of records, and it all worked fine
Sorry but that was an extrememly poor business decision. You just do not do this. You cannot reply on desktop application sfor business critical storage and or processing. Be it a middle tier maybe but even at that when and if I see MS Access or any thing such as Excel etc...being used to provide information to the end community it means the people that came up with the specifications all the way down to the development and implementation failed horribly at doing their job correctly. It is an uncontrolled environment and so unstable you're better off attempting to walk a high wire without having two legs
My 2bits and I'll leave it alone now.
[sub]____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]
I never said it was a business critical application, just that it worked with millions of records in it...
also, the general concensus is that access can handle about 20-30 concurrent users, however in my opinion, concurrency does depend heavily on how you design your system, e.g. you will have less problems if you don't use bound forms...
I know of a corporate-wide application where I work that is built entirely from Access. It's a slow snail, and it takes ~ 20 minutes to "submit" files to a source system.
To make a long story short, I'm with onpnt, don't use Access to try to handle large databases.
I've made a small fortune taking business critical solutions developed in Access (and Excel too for that matter) that ended up totally hosed/out of control/impossible to maintain-support and turning them into REAL business critical solutions using SQL Server and (choose a UI programming language - Access included!).
Just because you CAN do a thing doesn't mean you SHOULD!
< M!ke >
Acupuncture Development: a jab well done.
Access applications are for rogue users who spread their little virus around the department. When the file size exceeds 2GB they come crying to us. When the coder's logic spits out incomprehensible garbage, they ask us to fix it.
"Sorry, that's not a supported application."
I'm with Mike. We upsize or replace Access apps at every opportunity.
I write a lot of applications in access, and use SQL server as the back end for nearly all of them. Our SQL server is not really that heavily used though, if it was I would consider leaving some access - only. What I really hate about access is the jet engine. I have written some queries that won't run in access (usually involving different calculations using data from multiple tables), but if I put the exact same tables in SQL Server, link to them, and run the query that way they work fine. This frustrates me to no end!
If you are adding 1 million rows per year, and your tables are even a little wide, I'd think you would outgrow access rather quickly. I am looking at an access db sent by a client right now for some data overlays and analysis that is 1.6 gb (performance is ATROCIOUS!). By my rough estimation, this has 5-6 million rows in it (3.2 million in the main table). So, as a short term solution, access will probably work for you. If you want something more dependable over the long term, go with SQL Server.
Hope this helps,
Alex
Ignorance of certain subjects is a great part of wisdom
Microsoft actualy used Access as the Meta-data store for Analysis services in SQL2K. You could upgrade it to SQL. I can't remember how many times the access DB would get corrupt due to the size of our AS definitions.
Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.