Josh Hicks

Hazem, SymmetricDS Pro does support MySQL log based capture in addition to trigger based capture. During the deployment process in the pro web console you can choose the capture type you would like. It will set up that node for log based capture at that point and your all set.

Please submit a pull request for the change you want and we can review it to part of the working branch.

Routing controls the data gaps so as data is routed it will adjust the gaps. Is routing running to completion without failure? There is a parameter that controls data gap expiration as well if you want to be adjusted. It will default to 1 day. purge.expired.data.gap.retention.minutes=1440

There is a DB Compare tool in the pro version. Otherewise you need to make sure there are not any outstanding batches, no data to route, and no batches in error.

You can achieve this with one central node(engine). Each site property file would have a property to identify its database on the central. For example : central.db.name Then in the site to central router put the target catalog name to the variable $(central.db.name).

You can just remove the channel and the purge will clean up old references to it where needed. Any pending changes will be lost on this channel.

Columns should be upper case, a .equals() on a string, and semi colons to complete statements. Try this: if (REGISTRATIONSTATUS.equals("Pending Check")){ // row will not be loaded return false; } else { // row will be loaded return true; }

You need transforms to change the table name. The same trigger will not work as it has different names at each location if you are setting up bi-directionally.