Database Replications
  |
 |
||
| Apps | Servers |
The management of copies of tables across a distributed database environment is replication. Replication may implicitly involve maintenance of all or some of the objects related to a table; e.g. Triggers, Indexes, Referential Integrities, and so on, so as to maintain database consistency at any point of time for all the databases.Depending on the Business Requirements or typical needs, Replication can assume various forms, in terms of, Replication Type, Object and Acceptable Propagation Delays.
Replication Types can be whether it is a one way Replication, like snapshot replication is a type of replication which merely copies data from Server A to Server B. n-way replication is a multi-master Replication, which copies the incremental changes originating from any participating server Group to the remaining servers in the Group. Merging Replication combines the daa from 2 or more servers and applies to the destination server.
On almost all replications, there is an acceptable time delay, referred to as propagational delay. This depends on the requirement specifications. At times, the need is almost on-line and real-time replication. In some different requirement, the object of replication could be to off-load the reporting needs and in such cases the acceptable propagational delay can be higher.
Associated to the complex n-way replications are certain replication confilcts and data integirty issues. We have resoultions available for such issues in terms of the way we configure and the features available for such remediation in different technologies.Far East—a region that bears considerable cultural and religious commonality.