topic Re: Latency for Non PK table, Source- Oracle and Target - Synapse in Qlik Replicate

Latency for Non PK table, Source- Oracle and Target - Synapse

gayatri235 — Tue, 13 Feb 2024 18:45:58 GMT

Hello All,

So we have a task where source is Oracle and target is Synapse , and all tables in that task dont have primary key .

Can anyone share few tips and tricks to improve performance of this task ?

Re: Latency for Non PK table, Source- Oracle and Target - Synapse

Dana_Baldwin — Tue, 13 Feb 2024 19:09:27 GMT

Hi @gayatri235

A unique index on the source & target tables may help.

Apart from that, we would need more details. Please increase logging for Performance to trace for 5 or 10 minutes, this will write to the log if it is source, target or handling latency.

Also, check the logs for any errors or timeout issues connecting to source/target.

Thanks,

Dana

Re: Latency for Non PK table, Source- Oracle and Target - Synapse

gayatri235 — Tue, 13 Feb 2024 19:22:55 GMT

ok, let me help you with the log.

Re: Latency for Non PK table, Source- Oracle and Target - Synapse

SushilKumar — Wed, 14 Feb 2024 07:10:33 GMT

Hello team,

Its always recommend having primary key against the tables which are participating into the replication. As and when Qlik replicate try to find the rows or columns on the target endpoint to perform DML . having PK info gathered from Source during metadata helps and increase performance.

Regards,

Sushil Kumar