As companies implement data integration across their enterprise, it can often lead to a data tragedy, whether that is complexity, high cost, outdated information, or even lost data. Let’s take a look at some common data tragedies and how data replication can help you avoid them.

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.

One of the most common replication patterns we see here at JumpMind is a three tier setup with a central, regional, and site group.  Retailers commonly use this approach with groups named: corp, store, and register.   However we often see setups that try to reduce this approach down to two tiers with a similar set of functionality.  Deciding between a two or three tier approach can be tricky and each may have advantages and disadvantages based on your needs.  This article will help to explain these differences and hopefully help in making the best design choice for your needs.

Quickly select and dynamically add tables to database synchronization using wildcard characters. This powerful feature can save time during configuration and even eliminate the need to make changes to configuration in the future. Since data capture triggers can be created from a schedule or on-demand programmatically, wildcard characters open up the possibility of new applications, such as using SymmetricDS database replication in Platform As A Service (PaaS) where new tables created by a client are automatically replicated between high availability servers. This article will demonstrate using wildcard characters to sync some tables while ignoring others.