Difference Between Apply Changes and Store Changes

[Ginni]

The major key points difference between Apply Changes and Store Changes :

Apply Changes	Store Changes
Utilized with RDBMS type target endpoints.	Utilizes with file based target endpoints.
Applies the changes in real time at target end.	Applies the changes after a certain time at target end.
Does not capture the changes in __ct table.	Captures the changes in __ct table.
To capture changes in partitions are not allowed.	Partitions can be created for a specific time to store the changes.

Any suggestion if anyone provides, is highly appreciated.

[Kent_Feng]

Hi @Ginni 

By definition, Apple Changes also called Change Processing, or Change Data Capture (CDC): Captures changes in the source data or metadata as they occur and applies them to the target endpoint as soon as possible, in near-real time.
Store Changes: Captures changes in the source data or metadata as they occur but does not apply them to the target.

In real life, Apple Changes are saved to your target table and Store Changes are save to the audit table or change table in your target database. For example, if your target table name is Table1, Apple Changes are saved to Table1 in target database so it would have all the up to date data same as the source Table1; while store changes are saved to 
- attrep_audit_table: if you choose 'Audit table' in Store Change Settings.
- Table1__ct: if you choose 'Change tables' in Store Change Settings.

Thanks

Kent

[john_wang]

In additional to @Kent_Feng comments:

1. Apply Changes: Supported by relational database management systems (RDBMS) such as Oracle, MySQL, and SQL Server, as well as streaming platforms like Kafka and similar systems.

2. Store Changes: Supported by RDBMS and file-based storage targets, including options like File target, S3, GCS, and others.

Whether you choose to enable 'Apply Changes' or 'Store Changes' depends on the needs of your project:

• If your goal is to replicate changes from the source to the target, synchronizing tables across two databases, then 'Apply Changes' is the appropriate choice.
• If you simply need to capture and store changes for later consumption by other applications, 'Store Changes' is more suitable.

Hope this helps.

John.

[Ginni]

Thanks @Kent_Feng for the detailed explanation. I really appreciate your efforts.

[Ginni]

Thank you @john_wangfor the comprehensive explanation. I sincerely appreciate your dedication and effort.

[john_wang]

Hello @Ginni ,

You're very welcome! I'm glad I could help. If you have any more questions, feel free to ask. Good luck with your project!

John.

[trimlesmike]

good