I've asked this before, but let me describe it another way, and see if anyone has any bright ideas:
My client has 3 offices. Each office needs to use same app (over MySQL). Each office needs (effectively) same database. Updates done at each office need to be used at other offices. Updates visibility not too time critical - overnight re-synch is acceptable. Ideal Solution: One central database, all clients at each office connect to it. BUT - geographically separate, telecomms costs prohibit live on-line access at reasonable speed to same database. Should I : a) Use a copy of database at each office. Log each update at each office, and apply these at night to other 2 databases. b) Use replication with link down until night-time, when replication method will do re synch for me. c) Some better solution you wonderful people out there are going to suggest to me, and I will say "Dohhhh, why didn't I think of that !" a) looks clumsy b) Don't know if replication model is appropriate. TIA David. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
