Best Practices for Setting Change Frequency in Qlik Replicate
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.
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.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
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.
