When to use synchronization - Connect_CDC - connect_cdc_mimix_share - aws_mainframe_modernization_service - 6.x

Connect CDC Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
ft:locale
en-US
Product name
Connect CDC
ft:title
Connect CDC Getting Started Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2026-02-25
ft:lastPublication
2026-02-25T19:01:02.274000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Connect
L4_Investment_Segment
Application Data Integration
L5_Product_Group
ADI - Connect
L6_Product_Name
Connect CDC

Use synchronization to set up a new replication target by populating empty tables before activating replication. In this case, once the tables have been synchronized they probably never need another synchronization because changes in the source table are continuously replicated to the target.

A second use scenario is that you normally keep online replication turned off and synchronize changes from the source table to the target table at periodic intervals. In this case, you are more likely to want the “sum-total” changes rather than all intermediate modifications.