In addition to replicating data changes from source to target you may also wish to populate a table on the target to monitor all events.  In this blog I will show you how to create a simple load filter that will record all changes captured by SymmetricDS into a simple audit table.  

There are some common mistakes when implementing a data replication solution that should be avoided. As I've helped companies use SymmetricDS effectively for database replication as part of their data integration strategy, I've seen the same mistakes and misunderstandings. In this article, I'll explain some of these pitfalls and give you some tips on what to do instead.

Both Oracle Advanced Replication and SymmetricDS provide database replication, which is a valuable tool for improving access to critical data that drives a business. While some common replication concepts are used across both products, there are some differences in terminology and configuration. Let's take a look at some of the scenarios for database replication and how both products accomplish them.

We have received many inquiries about the architecture of SymmetricDS lately.  I think the user’s guide does a nice job of laying out how to implement and configure SymmetricDS, but we have noticed (after taking a step back) that it doesn’t provide a concise, technical overview.   You can probably piece everything together from the guide, but it is probably worth some effort to describe how SymmetricDS works under the covers.  We’ll be updating the documentation with this information in the near future.