SymmetricDS

SymmetricDS 3.13.2 and 3.12.14 are released! This bugfix release includes log4j 2.17 to address the recent Apache Log4J vulnerability. (SymmetricDS 3.11 and older are not vulnerable.) One additional fix was made for 3.13.2: Initial load stuck in loop with "there is no content to read" error 3.13.2 changelog 3.12.14 changelog

SymmetricDS 3.13.1 and 3.12.13 are now available. This bugfix release addresses the recent Apache Log4J vulnerability. (SymmetricDS 3.11 and older are not vulnerable.) Here are some issues fixed: Upgrade log4j to fix log4shell vulnerability ... [More] Multiple active trigger histories result when more than one trigger assigned to a table During a full load do not ok existing batches for the same load id Data mapping is incorrect on an insert fallback to update potentially when column count on target is not the same as row data SymmetricDS 3.13.1 changelog SymmetricDS 3.12.13 changelog [Less]

If the source data to be replicated resides in a read-only (select only) database, common replication approaches like log based or trigger based are not an option. Through some additional configuration and a few prerequisites on the source database SymmetricDS can still be used for replication in a time based approach.

If the source data to be replicated resides in a read-only (select only) database, common replication approaches like log based or trigger based are not an option. Through some additional configuration and a few prerequisites on the source database SymmetricDS can still be used for replication in a time based approach.

There are three primary methodologies used in database replication: log based, trigger capture, and time based. Determining which of these approaches is best for your use case can be difficult without understanding the limitations of each type. This article will help identify the differences, pros, and cons of each approach.

There are three primary methodologies used in database replication: log based, trigger capture, and time-based. Determining which of these approaches is best for your use case can be difficult without understanding the limitations of each type. This article will help identify the differences, pros, and cons of each approach.

There are three primary methodologies used in database replication: log based, trigger capture, and time based. Determining which of these approaches is best for your use case can be difficult without understanding the limitations of each type. This article will help identify the differences, pros, and cons of each approach.

There are three primary methodologies used in database replication: log based, trigger capture, and time based. Determining which of these approaches is best for your use case can be difficult without understanding the limitations of each type. This article will help identify the differences, pros, and cons of each approach.

SymmetricDS 3.13.0 is now available! This minor release fixes 6 issues and makes 13 improvements, including: Faster startup time by checking if sync triggers or auto create tables need to run Cleaner shutdown that closes connections and stops jobs ... [More] to properly reclaim resources Changing parameters no longer restarts all jobs, avoiding interruptions Added purge of trigger history to keep system lean and fast Improved purge performance of extract requests See the changelog for more details. [Less]

SymmetricDS 3.12.12 is now available! This patch release fixes 31 issues, including: Loading data when same column name on table twice in different cases Handle change to primary when using single-value transforms Fix foreign key resolution when ... [More] primary key contains newlines Fix for conflict handling when using user-defined types on PostgreSQL Fix for using tables with unitext column and no primary key on Sybase Error with LOB and geometry types on same table in Oracle Fix timing issue in service wrapper for Amazon EC2 Fix purge error on Firebird with dialect 1 See the changelog for more details. [Less]