How big is too big!!!

[LTunnicliffe]

All right... I have to have written proof, so my co-workers will believe me.

We have databases that are approaching on a gig big, without being repaired/compacted. Is this healthy and what problems can this cause in the future (or are currently causing)?

Thanks for ya'lls help!

 

[texasalynn]

Here are some places to look:

http://dbforums.com/showthread.php?threadid=778166&highlight=size+limits

http://www.utteraccess.com/forums/s...5&Old=allposts&Main=9714&Search=true#Post9748

hth
texasalynn

 

[SydneyGeek]

I'd suggest doing a repair/compact regularly. With that much stuff in the db it would be a shame to lose it due to data corruption...
Repair/Compact is (or should be) part of the regular care and feeding of any database -- Access or otherwise.

Denis

 

[Smitty]

Loren,

You should seriously consider compacting the database(s).

Every time you import data into Access or copy a table, Access stores those records and doesn't get rid of them.

E.G. I import 750,000+ records into a single database file each week. It goes from 46Mb to 100+Mb when I do. When I compact, Access releases the unused data and it's back to 46Mb.

(A bit of information I got from Microsofa when they still gave out information).

Hope that helps,

Smitty

 

[bat17]

And if your database is not already split into a Front End/ Back End set up I would reccomend doing that as well!

Peter