« Lies, Damned Lies, and Statistics | Main| So You Think the User Interface Does Not Matter »

Data Integrity and Replication Conflicts


Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

A contributing factor for many data integrity issues is replication. Though the Notes replication technology speeds application deployment to diverse environments, it can also erode data integrity when remote users attempt to merge conflict documents post-replication. Resolving save/replication conflicts is typically a manual process that is very time-consuming, especially with large database installations, and is often ignored.

Data management policies should include guidelines on how to deal with replication conflicts. This can even be done on a per application basis. There should be clear instructions describing when to merge two conflicts, and when to delete conflicts. Decisions for what action to take regarding replication conflicts should not be left up to the user who discovers it.

Posted by Scott Johnsen On 07/13/2009 | Digg This |

Comments

Gravatar Image1 - An unscientific poll conducted here reveals that 93% of users, when faced with a save or replication conflict, simply delete the child document to remove the conflict. Often, without even trying to determine the differences between the two versions.

Would their behavior be different if there were better/more convenient ways to spot the differences? I wonder.

Posted by Nigel Cheshire At 10:50:31 AM On 07/13/2009 | - Website - |


Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)