Example

 

How a schedule is created for the remote database DESTDB.

dmSQL > CREATE SCHEDULE FOR REPLICATION TO destdb
BEGIN AT 2000/1/1 00:00:00
EVERY 12:00:00
IDENTIFIED BY User Password;

For the above example, all destination tables on the DESTDB database are updated
starting at midnight, New Yearˇ¦s Eve. Destination tables are subsequently updated
every day at midnight and noon. Note that a source database can have multiple
schedules on different databases, and can write to databases that use different database
engines. Any time the source database has a change written to a source table, the
change is recorded in the replication log file directory as one of many replication log
files. When the distributor daemon is activated, it translates these files into ODBC
calls that are then sent to the destination databases. Using ODBC calls to update
destination tables allows ATR to be performed onto any type of database that supports
ODBC. This is known as Heterogeneous ATR. Replication log files that have been
sent to the distributor daemon are deleted after use, and information about them
recorded in the ATRP.LOG file in the Database Directory. Errors returned by the
distributor or subscriber daemons on the destination database are recorded in the
ATRERROR.LOG file in the Database Directory. For more in-depth information on
ATR, please refer to the Database Administratorˇ¦s Guide.


Related topic:

Asynchronous Table Replication Settings