Database size

[test]

Since the size of the MS Access database is limited, what
should I do when the data in the database exceeds this
maximum limit?

 

[Jeff Boyce]

Migrate to something bigger, SQL-Server for example.

Jeff Boyce
<Access MVP>

 

[Guest]

This can't be done as this is our client who is working on
Access. Is there any other way?

Thanks.

 

[Jeff Boyce]

Without more details, it's kind of tough offering suggestions. However,
another possibility might be to split the data into different back-ends
(TableA in dbA, TableB in dbB, TablesC, D, E, and F in dbC, ...), then use a
single front-end to link to them.

If you are facing that much data, you may be straining to use Access in a
situation for which it was not designed.

There are non-MS SQL-type databases, if there's an issue with the
manufacturer...

Good luck

Jeff Boyce
<Access MVP>

 

[John Vinson]

Since the size of the MS Access database is limited, what
should I do when the data in the database exceeds this
maximum limit?

If you really have over two billion bytes of data, you should really
be looking into a client/server application such as SQL/Server or
MySQL; you can still use Access as the frontend. Are you regularly
Compacting the database? How many million records do you have (or
expect) in your largest table? Are you storing graphical images in the
table? If so, bear in mind that Access is LOUSY at handling graphics;
they'll bloat a database very rapidly. It's better to store the images
externally and just store path and filenames to the images in a Text
field.

 

[Dee]

I have been trying to find the maximum size an Access 2000
database can be. We have been experiencing a lot of
corruption and need resolution. The database seems to
reach 1.99 GB when it gets corrupted. Once compacted it is
500 MB. I am thinking about splitting out several data
tables into seperate tables. Do you know the maximum size?

 

[John Vinson]

I have been trying to find the maximum size an Access 2000
database can be. We have been experiencing a lot of
corruption and need resolution. The database seems to
reach 1.99 GB when it gets corrupted. Once compacted it is
500 MB. I am thinking about splitting out several data
tables into seperate tables. Do you know the maximum size?

2.0 GB. See "Specifications" in the online help.

Regular compaction is *essential* maintenance. If you don't have 2
GByte of actual data, I'd suggest compacting whenever the database
gets above a gigabyte, rather than redesigning it.

I hope you do have a split database with the Tables in a backend and
the user interface in the frontend, especially if it's a multiuser
system! This by itself will prevent a lot of bloat and corruption (at
the cost of somewhat slower performance under some circumstances).