Store change settings

[desmondchew]

Hi,

We normally create tasks with Full Load, Apply Changes but not Store Changes option when we setup a replicate task.

We do receive changes at the destination target even without store changes.

Can you share when is store changes require?

Thank you.
Desmond

[DesmondWOO]

Hi @desmondchew ,

When you use the 'apply changes' function, any changes made will be applied to your target table directly. 

When you use the 'store changes' function, there are two options: Change tables and Audit table.
- Change tables: 
Replicate creates a table e.g. <your table name>__ct on the target and save the change events in the change table. Details can be found in this link Using Change Tables.

- Audit table
Similar to Change Table, but Replicate store changes to all tables in a single Audit table on the target. Details can be found in this link  Using an Audit Table.

Regards,
Desmond Woo

[desmondchew]

Hi,

So using 'store changes' is actually are keeping an audit trace? If we don't need the 'audit" logs, using 'apply changes' it will be faster as we have the same functionality. We get the DDL replicate across minus the "audit" changes?

[Steve_Nguyen]

So using 'store changes' is actually are keeping an audit trace? 

ans: yes , but each table would have a __ct by default.

If we don't need the 'audit" logs, using 'apply changes' it will be faster as we have the same functionality.

ans: you would have to test to see if this is faster in your environment or not.

 We get the DDL replicate across minus the "audit" changes?

ans: check link the john provide on what information is in change table vs audit.