Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a complicated system that is pushing data into an MDB file.
The mdb filesize is currently at 40MB.
Did anyone had any experience with larger mdb files and could tell me what is the maximum capacity that it will be still operational? (if it’s dead slow at 150mb i don’t call that operational).
Thanks!
David already gave an answer for the maximum file size, so I’ll address the speed issue.
Size of the DB alone isn’t going to be deterministic of speed. 150 MB is nothing for an Access Jet DB. I’ve run Access MDB files well into the GB range with no noticeable performance issues. However, the larger the individual tables get the more important it will be to implement a good indexing strategy and architect the databases for optimal performance. This is pretty much the case with just about any DB engine, Access Jet included.
Also, the limit for an MDB isn’t necessarily the upper limit on the total size of the data you can manage in a single application. With some clever architecture you should be able to split the data into multiple MDB files and link them into your application.