topic Re: Best Practices for Setting Change Frequency in Qlik Replicate in Qlik Replicate

Best Practices for Setting Change Frequency in Qlik Replicate

toni_lajsner — Wed, 19 Mar 2025 14:12:53 GMT

Hi all
One of our sources is IBM iSeries2 , and at the moment, we are checking for changes every 180 seconds. However, when I say it out loud, it seems that might be too frequent for what we actually need.
I am wondering how others handle connections and how often you check for changes.

Re: Best Practices for Setting Change Frequency in Qlik Replicate

john_wang — Wed, 19 Mar 2025 14:43:07 GMT

Hello @toni_lajsner ,

The "Check for changes every" parameter controls how often Qlik Replicate checks for new changes that are generated and ready for capture. When Qlik Replicate reaches the end of the journal, it pauses for the specified interval before checking again for new changes. By default, this interval is set to 5 seconds, but it can be customized based on the acceptable latency for your use case.

Hope this helps.

John.

Re: Best Practices for Setting Change Frequency in Qlik Replicate

toni_lajsner — Thu, 20 Mar 2025 05:03:11 GMT

Hi John

I am aware of how the "check for changes" feature works. This is why we have set it to 180 seconds instead of the default 5 seconds—having it set to 5 seconds on our system generates continuous data, which results in our Azure endpoint receiving a large number of hits, causing unnecessary costs. My question is focused on best practices and what intervals other customers with the same source are using.

So the question is mostly about sharing knowledge.

Re: Best Practices for Setting Change Frequency in Qlik Replicate

SushilKumar — Thu, 20 Mar 2025 09:43:37 GMT

Hello @toni_lajsner

It is all About the Customer environment and business SLA to maintain. The customer is the one who may set the Gap between 5 Seconds to 1 hour.

Regards,
Sushil Kumar