Clienteling isn’t a new theory. It can be traced back hundreds of years when shopkeepers …
Cloud-native POS platform for seamless omnichannel customer experience.
A single hub for all promotions campaigns.
The most advanced synchronization solution for databases and file systems.
Data configuration and batch automation across different disparate systems and vendors.
The new release of SymmetricDS 2.4 will help you:
A table on the source database can be mapped to a table on the target database even if they have different names and they are located in different schemas. Using the web console, the user can specify each column from the source table that replicates to a column on the target table. Since only the specified columns are replicated, this also makes vertical data filtering easy.
A new set of powerful transformation features make it easier to transform, merge, and supplement tables during replication. Transformation can be performed with access to the source database during the extraction phase, or during the loading phase with access to the target database. The web console makes mapping tables and specifying transformations as easy as point and click. Add new columns with constant values or variables, or provide a SQL query to lookup values from another table. Multiple source tables can be merged to synchronize a consolidated target table. Or transform a single row from the source database into multiple rows on the target database. Specify different mappings based on whether the change is insert, update, or delete. If the built-in transformations don’t meet your needs, then paste in a Beanshell script that can transform the data however you need.
While large object replication of binary (BLOB) and character (CLOB) data has been possible in the past, this release includes stream oriented handling of data. Normally, the change data capture system records the LOB to the sym_data table. Each database system has a limit on the amount of data that can be captured for each row. Now the user can enabled the “Use Streaming LOB” option to skip the data capture and stream the LOB from the database instead. This makes it possible to replicate much larger objects than were previously supported.