data synchronization

  • "Hands Off" Recovery

    Anyone who has been on a night time support rotation can relate to the 3 AM phone call that gets you groggily out of bed, has you fixing some simple, but important problem, and then leaves you staring at the ceiling by 4 AM wondering if you should just go into work, because you know you aren't getting back to sleep. All of the engineers in our office have been there, done that, and didn't like it very much. That's one of the reasons we focus so much on resilient operations for SymmetricDS including our "Hands Off" Recovery of data synchronization. "Hands Off" recovery is pretty much exactly what it sounds like. SymmetricDS has been built from the ground up to recover and keep databases in sync without manual intervention any time it possibly can.

  • Batch Screen Improvements in SymmetricDS 3.9

    In the SymmetricDS 3.9 release, many user interface changes have been made to improve usability and display more information. One area of focus for these improvements are within the Incoming and Outgoing Batch screens. These changes provide a cleaner and more uniform representation of the data displayed on both screens.

  • Permissions

    All SymmetricDS synchronization configurations require database connectivity. As a result questions often arise around the topic of database permissions. Specifically what permissions are required for the SymmetricDS user and do the SymmetricDS tables need to run in the same catalog or schema as the tables to be synchronized.

  • Stop Guessing if Your Data is Correct

    SymmetricDS promises to sync your data, but how do you know it really worked? How do you really know 2 databases are in sync? Or, maybe you have well-meaning users that come along after the sync, changing data unexpectedly, and throwing production out of whack.

    Whatever the case, wouldn’t it be nice to be able to compare any 2 databases, and know exactly what the differences are and be able to prove they are in sync? That’s where a new, experimental feature of SymmetricDS comes in. It’s called simply dbcompare. Dbcompare is slated for SymmetricDS 3.8, but if you watch closely, it’s fully included starting in SymmetricDS 3.7.30.

  • Three Tier Replication Done in Two Tiers

    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.