[AccessD] Replication concept

Hi John:

Makes sense to me. I am the systems guy for a small site with only two
offices and the system has been replicating back and forth for years. The
sync process at these sites only runs twice a day, noon and evening. There
have been rare occasions when there has been data collisions but they do not
halt any processes. I have got into the habit of checking the sites once
every couple of weeks by going directly into one of the BE DBs and any
duplicates issues will popup and request resolution. The activity in each
office is moderately low, thirty entries each per day and the dup errors are
about once a year (maybe).

HTH
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Colby
Sent: Monday, May 05, 2003 8:16 AM
To: AccessD
Subject: [AccessD] Replication concept


Folks,

I just wanted to run an idea past you guys.  One of the concerns expressed
by my client's users was the time required for changes to ripple around if
we used the "standard" replication scheme of a BE on every desktop.  It
occurred to me that perhaps the client could create 2 or 3 "servers" where
each server had a copy of the BE.  Instead of 25-30 users all linked into a
single back end, have 10 users each (roughly) linked into one of three BEs.
Those three BEs then replicated amongst themselves.  The business breaks
down into three distinct sets of users (business groups) so that perhaps all
members of a group could link to the same BE, thus getting instant access to
the changes from it's group and yet still have rapid access to changes from
the other two business groups since the replication circuit would consist of
only three BEs instead of 30.

This would allow other advantages as well if the client wanted to pursue
them, such as segmented networks, with each server having it's own routers
and thus the traffic routed to each server would drop considerable.

My question to you is, does the idea of a small number of BEs (probably 3),
sitting on servers, replicating amongst themselves, linked to the FEs on
users desktop machines - does this idea make sense?

John W. Colby
www.colbyconsulting.com


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com