Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, I'm wondering if its possible to replicate(update) only specific rows in the table without dropping and/or truncating the table?
Thanks ahead!
@Aegis here are a few examples from the Knowledge Base.
https://community.qlik.com/t5/Knowledge/Filter-Deletes-in-Replicate/ta-p/1801945
>> if its possible to replicate(update) only specific rows in the table
Have you consider a 'benign' update to the rows needed to be re-applied?
Simple: UPDATE <table> SET <pick-any-column> = <pick-same-column> WHERE <your selection criteria>
The exact execution of this depends somewhat on the source and target platform. If I recall correctly does apply these benign updates to the targets, but does not executed the store-changes in __ct tables for them.
Best thing to do is a sample task with just 1 table for your source/target and software version, start, wait, enable full verbose target_apply (and optionally source_capture), apply a benign update or two, reduce logging and check both the target tables for the desired effect as well as the rep-task log. Trust but verify!
Hein
Hey @Aegis ,
Within the expression builder, you can set up logic, expressions or functions based on SQLite to update records.
User Guide for reference:
Best,
Kelly
@Aegis here are a few examples from the Knowledge Base.
https://community.qlik.com/t5/Knowledge/Filter-Deletes-in-Replicate/ta-p/1801945
>> if its possible to replicate(update) only specific rows in the table
Have you consider a 'benign' update to the rows needed to be re-applied?
Simple: UPDATE <table> SET <pick-any-column> = <pick-same-column> WHERE <your selection criteria>
The exact execution of this depends somewhat on the source and target platform. If I recall correctly does apply these benign updates to the targets, but does not executed the store-changes in __ct tables for them.
Best thing to do is a sample task with just 1 table for your source/target and software version, start, wait, enable full verbose target_apply (and optionally source_capture), apply a benign update or two, reduce logging and check both the target tables for the desired effect as well as the rep-task log. Trust but verify!
Hein
@Aegis did any of the reply help ?