I converted my database to a Design Master on a local server in PA, and created 2 replicas which reside on servers in MA and Mexico. It seems to be running well and my plan is to do the following on a weekly basis:
1. Pull data from various production systems into the Design Master
2. Compact and Repair the Design Master
3. Synchronize the 2 replicas with the Design Master
I have automated item 1 and in researching how to automate items 2 and 3, I read posts that say you should not compact and repair a database unless it is resident on the same machine that runs the compacting program. I'm not clear on what that means. My database resides on a local corporate server but MSACCESS.EXE (assuming the compaction program resides within) resides on my laptop's hard drive. Is it suggested that I move my Design Master to my laptop's hard drive in order to compact? I read that moving or renaming any of the contents of a replica set is a NO-NO.
Additionally, most of the posts I've read on compacting refer to databases that have been split. I elected not to do that some time ago for simplicity. Should I reconsider?
Thanks for any help,