DML Output in Qlik Replicate

[rgulati]

Is it possible to generate DML statements instead of replicating to a destination ?

[john_wang]

Hello @rgulati ,

Welcome to Qlik Community forum and thanks for reaching out here!

You may enable the store changes to meet your need. This feature stores  all events (Update,Insert,Delete) in the associated change table (__ct), each table owns itself __ct table.

Please note that in some scenarios, change events are captured as individual row-level changes, rather than reflecting a single original DML operation from the source. For example, consider the following DML statement executed on the source side:

update tableA set ColA=something where ColB='condition';

If this operation affects 10 rows, the change table (__ct) will contain 10 separate DML entries instead of one single operation. These individual entries may also include other columns that help distinguish between the affected rows.

Hope this helps.

John.

[DesmondWOO]

Hi @rgulati ,

I've attached a screen capture of the change table (__ct) for your reference.

In the picture above, id, c1 and c2 are the columns of the target table, while the other columns are Qlik Replicate's header columns.

Regards,
Desmond