Database Size Too Large

[GeoDude]

I work for an Oil Company and we have a production database that is
usually around 300 megs. For the last couple of days I come in the
morning and the size is around 1.4 Gigs. I run compact and repair to
bring the size back to 300 megs.

I need help in figuring out what is causing the size to increase. We
update in the mid afternoon and that's not causing it. If anyone has
any advice I would greatly appreciate it.

Ivan

 

[Pieter Wijnen]

I assume you have split your db into front/backend
if so do consider using a "proper" db for the backend (mssql/oracle) - as
access tend to bloat due to it beeing a filesystem db (rather because of
related problems - but ....).
else split it at once!
btw you can use the jetcomp utility to "automagically" compact the db
(should still be avaiable from ms...)


hth

pieter

 

[Alex White MCDBA MCSE]

Hi,

this situation normally happens if there are a load of
updates/deletes/inserts going on in the database, you will need to review
all the processes that are running on the data to see which one is the
issue.

I have a few clients where I am compacting the database everyday via a batch
file.

http://support.microsoft.com/?scid=kb;EN-US;273956

This is normally the point where I create an empty database with the all
tables and import record by record from the old database, if that does not
work in resolving sizing issues then I have to look deeper at what is being
modified and how often. In a few cases this problem has been the last push
to move to SQL although I am not recommending that in this case.

Hope it helps.