Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello all ,
Can anyone tell , how the deleted records are processed by Qlik Replicate ?
Thank you
Ionut D.
Hi Ionut,
Thanks for reaching out. Could you please elaborate more on what do you mean by "deleted records are processed by Qlik Replicate"?
Is there something specific you'd like to know? As a rule of thumb if the settings are as default, Replicate will read the records that were Deleted on the Source and apply the DELETE event in the target as well. Please note that a table with Primary Key is crucial in these scenarios, as the lack of it might impact negatively performance.
Regards,
Pedro
Hi @deaconescu
I believe @Pedro_Lopez 's comment on a PK being defined on the table relates to the performance of the task. Without a PK defined on the target table in a traditional relational database, a full table scan has to happen on the target database in order to delete the rows, which takes more CPU/memory on the target than it would if a PK were available.
Thanks,
Dana
Hi Ionut,
Thanks for reaching out. Could you please elaborate more on what do you mean by "deleted records are processed by Qlik Replicate"?
Is there something specific you'd like to know? As a rule of thumb if the settings are as default, Replicate will read the records that were Deleted on the Source and apply the DELETE event in the target as well. Please note that a table with Primary Key is crucial in these scenarios, as the lack of it might impact negatively performance.
Regards,
Pedro
Hi Pedro ,
And thank you for your response .
It was a general question from customer , they wanted to know if Qlik has any impact on deleted records .
However, from you reply , should I understand that if the table don't have the Primary Key it will lead in discrepancies between source and target ?
Thank you
Ionut D.
1. first look at the user guide :
https://help.qlik.com/en-US/replicate/November2022/Content/Replicate/Main/Introduction/Home.htm
2. look at what is your source and target endpoint and check to see any limitation.
Hi @deaconescu
I believe @Pedro_Lopez 's comment on a PK being defined on the table relates to the performance of the task. Without a PK defined on the target table in a traditional relational database, a full table scan has to happen on the target database in order to delete the rows, which takes more CPU/memory on the target than it would if a PK were available.
Thanks,
Dana