Bridge data between databases with data synchronization by using channels to re-order data when the dependencies in each database are different. Each application can model its data differently, so a parent row in one database might map to a child row in another one. Instead of using data transformation to lookup and add dependent data, the order of captured data can be changed to match the constraints of the target database.

When integrating data from one database to another, sometimes the schemas are not the same. JumpMind has come across a number of projects where there was a need to transform a very denormalized database into more of a canonical or normal form.

SymmetricDS has always provided hooks for data transformation, but in 2.x we have made it far easier to add custom data transformations with just a bit of XML configuration and simple transformation scripts.

SymmetricDS has for years been a robust, reliable solution for synchronizing data between multiple databases and multiple database platforms. With SymmetricDS 2.4, SymmetricDS has expanded to also prove data transformation capabilities while synchronizing. The data transformation is performed via configuration settings in new SymmetricDS configuration tables, in a manner consistent with and familiar to existing SymmetricDS users.

The open source SymmetricDS 2.4.0 database replication engine is released for general use by the community. While this is a minor revision, it delivers some cool new features!

This is the second part of a series on synchronizing Android SQLite databases using SymmetricDS. The last article talked about how to embed the SymmetricDS Android client into an Android application. This article will provide an overview of the central server and how it can be configured to synchronize the sample Notepad database.