Two Gig Limit - Invalid Argument on EVERYTHING

tkpstock

Cubicle Warrior
Local time
Today, 13:36
Joined
Feb 25, 2005
Messages
206
I've apparently hit the two gig limit in access. The database won't let me compact/repair. it wont let me save changes to tables. I can't open access by itself and repair the external table. I'm sure that the database could be shrunk down if I could get it to do the repair! I get an "Invalid Argument" error on everything I try to do.

Anyone experience this? Anyone have any suggestions?

Thanks!
 
Can you start a new MDB and import from the old db? Does using the <SHIFT> key make any difference?
 
RuralGuy said:
Can you start a new MDB and import from the old db? Does using the <SHIFT> key make any difference?

That's what I ended up doing - I had to trash the 2-gig one. What a pain! I can almost see Bill's thought process on this one:

Hmmmm.... Access is pretty robust. How can I get people to buy SQL Server if they can get Access so cheap? Oh! I know! I'll put an arbitrary limit of 2 gigabytes on Access to force people to use my more expensive product!
 
I'm of the school that leaves "Compact on Close" checked even when released.
 
RuralGuy said:
I'm of the school that leaves "Compact on Close" checked even when released.

It was checked - but I exceeded the limit during some updates. The compacted version was over 1.5 gigs (one table has over 5.6 million records). When I tried extracting a subset of those records using a "select into" create table query, that bushwacked the whole thing. When it tried to compact, that's when I started getting the "invalid argument" error.

Oh well, I've dragged everything into another database and all is well...
 
The limit applies to individual .mdb files. You can use a separate .mdb for each table and link them to your front end.
 
nieleg said:
The limit applies to individual .mdb files. You can use a separate .mdb for each table and link them to your front end.
RuralGuy said:
I get the feeling you have not split your Application into FrontEnd and BackEnd. Here's a link on the topic. Split your MDB file into data and application

There is no front end. I've written a couple of small subs and functions, but there are no forms, macros, etc. and only a few queries (not enough to bulk up the db.)

The size of the DB is totally dependent on the one table that has over 5.6 million records - all the other pieces are relatively inconsequential.

Enough on this topic - I've resolved the problem for now...
 
Ouch! For that many records, you are, indeed, reaching the limit. Here's a thought on how to safeguard yourself.

Every so often, export the big table to a .CSV or .TXT file or some other reasonable format.

Trash the big table by deleting everything in it.

Now compact and repair the remnants.

Now re-import the .CSV or .TXT file.

Another way to protect yourself is to consider whether the records might be subject to life-cycle management techniques. In which you eventually declare the records "obsolete" and remove them from your primary. (Again, export to another format and reclaim the space. Import to your history database.)

Without knowing what you are doing, it is hard to be more directly constructive in terms of ways to protect your data.

I'll make one more suggestion. Look at your machine's physical memory and swap space. I would strongly suggest that you max out the box and the swap file. When making lists of data at that level, you are looking at 25 Mb just to hold the pointer list that corresponds to a single sorted query. Your database growth rate makes most of our puny little DBs pale by comparison.
 
Thanks Doc.

It's actually a database which stores geographic features for every country on earth. The database itself is expendable - the data is publicly available and merely being cleaned up for an Oracle implementation which I'm currently building. It was just easier to clean up in Access than it was in Oracle and I didn't want to bog down the Oracle development server by the procedures and queries that are taking sometimes hours to run. (and the Oracle development server is small and SLOW, I already crashed it once by filling the archive log!).
 

Users who are viewing this thread

Back
Top Bottom