Save / Replication Conflicts

I have a database that is used world wide.  But my users in the far east are having to make local copies of the database and using it that way ( due to infrastructure issues ).  When they replicate their local copy document back to the production database, I am having many Save Conflict errors saves.  Is there a way to stop this from happening?  Any ideas of how to address this?
Who is Participating?
qwaleteeConnect With a Mentor Commented:
Sounds like they are editing each other's documents (or, at least, they all touch the same documents). I can only suggest that you either:

1) get them a local server


2) have every transaction immediately followed by a client-based replication

Otherwise, you'll have to deeply analyze the application's technical structures and usage structures, and possibly redesign itm inlcuding a potentially difficult migration.

Note: If you use a central counter to assign "serial numbers," that would be something you NEVER want to do except in a single-replica environment.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.