|
|
|
-
Bi-directional Data Synchronization – Replicator does not put any constraint on
changing data in databases. Changes can be done to any/all databases involved in replication job
and data integrity will be maintained.
-
-
Supports replication across heterogeneous database – Replicator supports
replication across any combination of supported databases. Data source on one end could be daffodil
db and SQL Server could be on other end. In the same job different datsources could be used in any
combination.
-
-
Conflict detector and resolution – Daffodil Replicator offers very strong conflict
detection and resolution functionalities that allow multiple users to send in changes from the
workstations simultaneously, while ensuring the integrity of the data. "paste a link to conflict
resolution document".
-
-
Partial data (Tables, Rows and column) Replication – A user can ignore the columns
that he do not want to replicate. Columns that does not allow insert, update and delete operations,
create problem in data replication. Can ignore the tables he don't want to replicate or can also
add filter to datasource for replication of required filtered rows.
-
-
Large datatype support – Replicator supports almost all data types of supported
databases. It also supports BLOB and CLOB replication.
-
-
Scheduling – This feature allows subscribers to schedule (Real Time or Non Real
Time) the replication process (Snapshot, Synchronize, Pull and Push).
Edit Schedule facility is also supported to edit publisher server name or port no.
(If publisher is running on different URL or Port from the URL or Port specified at time of add
Schedule).If a user no longer need a schedule and wants to remove it, it can be done by
Remove Schedule facility.
-
Platform independent synchronization – 100% Java enabled client and server
components allow Replicator users to work platform independently.
-
Debugging – Replicator is providing the facility of
debugging using
Log4j.jar. In this file, user can set the logging option as per his requirement.
|