Replicating and Synchronizing replicate databases

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm working on a database that needs to be replicated but had a couple of
general questions about the process. Once you replicate the database, what
do you do if you want subsequent replicants (i.e. multiple copies that data
can be entered but can all be synched?). Do you just continue to make
replicates from the the first generation of replicates, or are do you make
copies of the front end? I guess it is unclear to me if there is a "mother"
version of the replicas or if all replicas are equal. I'm also not clear what
happens after you synch the data. We may need to change the structure of
some tables, do we synch the replicas and then change the structure to one
version and make new replicas from that? Thanks in advance for your help.
 
I have a few databases out there that use the synchronize. You'll basically
have 2 databases. (1) Design Master (2) Replica. What I found that works
best, is I put the Design Master on a server that only I have access to. I
put one Replica (what I call the "Master") out on a shared server that
everybody has access to. I give everybody else a copy of that replica for
their personal computers. I then have everybody synchronize to the "Master"
on the shared server.

Then I can make changes to the "Design Master" whenever I want, and only
synchronize it to the "Master" when I am ready to release the changes. This
also works well, because if you have a lot of people synchronizing, you can't
be in the db while it's being synched. This way, you can make design changes
without interrupting the flow of work.

I hope that helps!
 
Back
Top