Bob Alston <bo********@yahoo.comwrote in
news:Hr****************@newsfe08.iad:
I have a system built using Access replication. After some
initial problems dealing with memo fields, it now seems to be
working well.
I am curious as to how frequently others Compress & Repair
replicated databases?
First off, is your app split, with your data tables in one MDB that
is replicated, and all your forms/reports/etc. in a separate MDB
that is *not* replicated? If not, that's much more important to fix
than worrying about how often you compact.
Compacting a replicated database is a bit more dangerous than
compacting non-replicated databases. This is because certain minor
corruptions that are easily repaired by a compact in a
non-replicated database cause a replicated MDB to lose replicability
(which means it can't synch with the other members of its replica
set any longer). Unfortunately, there's no way to tell if you have
this kind of problem -- it is only revealed after the fact, when
replicability is lost.
Thus, I'd recommend regular maintenance compacts on a replicated
back end at a lower frequency than on a non-replicated back end. If
you're compacting your non-replicated MDB every day, I'd recommend
every week for a replicated MDB. Keep in mind that the other
replicas in teh replica set function as backups, so you're not in as
much danger of data loss as you are with a single non-replicated
MDB. And if you implement a replica farm, you can have very good
coverage in terms of recovery from the loss of any single replica.
--
David W. Fenton
http://www.dfenton.com/
usenet at dfenton dot com
http://www.dfenton.com/DFA/