Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
I have two qilk replicate regions A and B connected with one source db and here my query is , which region will get first updates from CDC and how do I conclude this? Can any one help on this!!
Thanks
Ramu.
Hi @ramu123
If you set your filters as shown below, starting from the left and working your way right, you will be shown the download links for 2023.5 latest available:
@ramu123 in theory the Replicate that is closer to the Source DB get the update faster.
you can enable source_capture to verbose see more detail information . NOTES do not set verbose too long as this takes lots of disk space on the log.
Hi Steve,
Thanks for your suggestion and Currently I'm using Qlik replicate May-2022 version , I would like to upgrade to Nov-2022 but I can found the software for 2023 ! Could you please help on this?
Thanks
Ramu.
Hi @ramu123
There is a link to the downloads page on this knowledge article: How to download Qlik Products - Qlik Community - 1906869
Thanks,
Dana
>>> which region will get first updates from CDC and how do I conclude this? Can any one help on this!!
No. Absolutely not. Nobody can help with this.
Is this a question originated by a (perceived?) business requirement, a 'nice to have', or just a curiosity?
If it is deemed to be a business requirement to control this, then you need to figure out why you think this is even relevant and then design an other solution such that it is no longer relevant. Perhaps by cascading update from source to A from A to B; Perhaps adding a replicate server local timestamp onto critical rows. Perhaps by using the commit or change time.
Even assuming that the A and B task are exactly the same, the main problem is that there will be two independent source-capture ""retryInterval" loops each at their own uncontrollable start time, with no guarantee/(Qlik)commitment to stick to that. Other activity on the respective servers, the network latencies (including distance as per @Steve_Nguyen ) and even the performance of data storage and the individual target databases can make the actual retry drift from the expected 'loop_start' plus <integernumber> times <retryinterval>.
I could even imagine that sometimes the perceived to be slower task, ends up committing a particular transaction on target faster because it was slow enough to catch that transactions end where the fast task did not yet see the end and is waiting a second or two before seeing if there is more data - including that end.
Cheers,
Hein.
Hello Team,
Would suggest Configure, test and puts source capture to verbose and this information help you get the relevant info which leads to conclusion and help to understand the reason and may lead to some conclusions,
Reagrds,
Sushil Kumar
Thanks Dana,
Here I would like to upgrade May-2022 to May 2023! Here I'm confusing which is latest patch version and How do I know full version with latest pactch in the dowload page?
Thanks
Ramu.
Hi @ramu123
If you set your filters as shown below, starting from the left and working your way right, you will be shown the download links for 2023.5 latest available:
Thank you very much Dana..