Compact and repair..

[paul123456]

We do a import process that adds about 100 MB to the database. even though the data that is temporaly imported is deleted. Is there any way...any way at all that at the end of my import i can automate a compact of the database without the front end users having to get off the database? as of now after the import i have to get everyone off the front end and do a compact and repair on the back end database...

Thanks, PAUL

 

[BobJacksonNCI]

Paul,

No, there's no way.

If you're repeatedly importing data into the same temporary table and then deleting the data (not the table), it doesn't much matter anyway...

Compacting is like disk fragmentation in that if you add and delete DIFFERENT items regularly, it's more important. But if you're essentially reusing the same space and aren't otherwise modifying the database, compaction is mostly an exercise.



HTH,
Bob

 

[paul123456]

Well my problem is that after about 10 imports..the Backend database gets to be about 1GB in size..when i compact it it goes down to about 100 MB.. is there anyway that a module can be made for compacting the database even if everyone is off the databse? from the front end?...this was at least i don't have to go to the backed of the databse and run it..i can just run it from the front end


Thanks, PAUL

 

[BobJacksonNCI]

Paul,

It sounds like you are creating temporary tables on the back end and then deleting them. If that's true, I'd recommend that you change to deleting the records from the temp tables and then append to them. Again, if my assumption is correct, by leaving the tables in place, you can add appropriate indexes and speed things up a bit.

I did an "advanced search" here and came up with some threads. They may or may not be of use to you, but does illustrate how others deal with compaction.

thread181-692164

thread705-642227

thread181-379233



HTH,
Bob