Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
gayatri235
Partner - Contributor III
Partner - Contributor III

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

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 ?

Labels (2)
3 Replies
Dana_Baldwin
Support
Support

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

gayatri235
Partner - Contributor III
Partner - Contributor III
Author

ok, let me help you with the log.

SushilKumar
Support
Support

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