<http://schema.org/articleBody>
" with the home grown replication systems that didn't work so well? 1) The 'two of everything' problem. You have two database schemas, two development teams, two maintenance schedules, two upgrade schedules, two management teams with different priorities. From now on, whenever one side wants to change, the other side will need to be consulted. 2) The 'separate but identical' problem. The actual mechanics of synchronising two databases are not trivial. For example, what happens when SQL Server is offline for ..."^^<http://www.w3.org/2001/XMLSchema#string>
<http://archive.midrange.com/midrange-l/201210/msg00299.html>