compacting database removes optmization?

  • Thread starter Thread starter don
  • Start date Start date
D

don

is true that compacting front end, erases query optimization and forces it
to be redone at next use?
(hearing I should turn off "compact on close", so keeps the optimization
routines intact for next usage..)
 
Don

Even if true (others understand "where the electrons go" better than I do),
I believe you could still use Debug|Compile to reconstitute the
optimizations after Compact/Repair.

A more cogent argument against using Compact on Close is because ****
happens.

If the only copy of your database is in mid-compact/repair when the voltage
hiccups, your db gets corrupted. If the only copy of your db is in
mid-compact/repair when the user running c/r decides to turn off his PC,
your db gets corrupted. If (fill in your favorite horror story here), your
db gets corrupted.

I suspect the real issue with Compact on Close is that you do NOT have a
backup copy in case the compact fails.

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
yeah I don't think that is true either...and I also don't know where the
electrons go as well as the MVPers...... time your query....do your compact
....and then retime your query....and see if it makes a difference....

I never remember a query taking longer due to a recent compact.....
 
Back
Top