Advertisement

[x]
Attachment Details

MSAccess:  Replication Strategy?

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.9
I have a replication question.

I currently replicate from a local design master to a single replica on a shared server that my users have access to.  Works just fine.

We are adding users at another facility in a different region of the country.  They can see the currently replica across the company network, but performance is very very slow for these remote users.

I am contemplating creating another replica to be located on a shared server more local to these remote users.

DM - Design master
R1 - Replica 1
R2 - Replica 2  
R1 and R2 don't actually need to share their data.  Just the app and table structures are common.

Question - What would be the best replication strategy?

1.  Create a "HUB" replica on a shared server.  R1 and R2 replicate only to the Hub.  DM replicates only to the HUB. Replication initiated periodically either from the HUB (by admin), or from R1/R2 (by user).

2.  DM replicates to R1 and R2 directly (no HUB).  Replication initiated from DM only (by admin).

3.  Same as option (2), except R1 and R2 can replicate to each other (by user).

There should be NO DATA COLLISIONS between R1 and R2, but not guaranteed.


Any thoughts?

Related Solutions
Related Solutions
 
Loading Advertisement...
 

Rank: Wizard

Accepted Solution by Rick_Rickards:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 

Rank: Wizard

Expert Comment by Rick_Rickards:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 

Rank: Wizard

Expert Comment by Rick_Rickards:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
Loading Advertisement...
20080924-EE-VQP-40 / EE_QW_2_20070628