<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CDC Taking Time in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/CDC-Taking-Time/m-p/2481343#M12705</link>
    <description>&lt;P&gt;Hello Community,&lt;/P&gt;
&lt;P&gt;We are facing performance issues while bulk insert and updates comes from source, as they too long to reflect on the target. we've checked both source and target availability, and everything seems fine, but the changes are accumulating at the target apply disk, as shown in the screenshot below.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pranita123_0-1726154830201.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/171620i69DF1CE67417E61A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pranita123_0-1726154830201.png" alt="Pranita123_0-1726154830201.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;we also enabled verbose logging for both source and target apply performance but haven't been able to identify any specific issue. any suggestions from our community member on how to resolve this would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;Pranita&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 12 Sep 2024 15:37:12 GMT</pubDate>
    <dc:creator>Pranita123</dc:creator>
    <dc:date>2024-09-12T15:37:12Z</dc:date>
    <item>
      <title>CDC Taking Time</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/CDC-Taking-Time/m-p/2481343#M12705</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;
&lt;P&gt;We are facing performance issues while bulk insert and updates comes from source, as they too long to reflect on the target. we've checked both source and target availability, and everything seems fine, but the changes are accumulating at the target apply disk, as shown in the screenshot below.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pranita123_0-1726154830201.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/171620i69DF1CE67417E61A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pranita123_0-1726154830201.png" alt="Pranita123_0-1726154830201.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;we also enabled verbose logging for both source and target apply performance but haven't been able to identify any specific issue. any suggestions from our community member on how to resolve this would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;Pranita&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2024 15:37:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/CDC-Taking-Time/m-p/2481343#M12705</guid>
      <dc:creator>Pranita123</dc:creator>
      <dc:date>2024-09-12T15:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: CDC Taking Time</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/CDC-Taking-Time/m-p/2481351#M12706</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/219875"&gt;@Pranita123&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Based on your picture, the changes are accumulated on the target side and offloaded to the disk. You can enable verbose logging on the TARGET_APPLY to see how long Replicate takes to update the target. Please also check if you have a large transaction or if transactions are taking a long time to commit. If a transaction is too large or takes too long, Replicate will offload the changes to the disk. Once changes are offloaded, performance may be impacted.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Regards,&lt;BR /&gt;Desmond&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2024 16:04:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/CDC-Taking-Time/m-p/2481351#M12706</guid>
      <dc:creator>DesmondWOO</dc:creator>
      <dc:date>2024-09-12T16:04:25Z</dc:date>
    </item>
    <item>
      <title>Re: CDC Taking Time</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/CDC-Taking-Time/m-p/2481389#M12709</link>
      <description>&lt;P&gt;Besides&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/125525"&gt;@DesmondWOO&lt;/a&gt;&amp;nbsp;comments:&lt;/P&gt;
&lt;P&gt;1. make sure the Change Processing Mode is in "&lt;STRONG&gt;Batch Optimized apply&lt;/STRONG&gt;"&lt;/P&gt;
&lt;P&gt;2. if the monitored tables have PK, if no it impacts the applying performance too.&lt;/P&gt;
&lt;P&gt;In a nutshell, the picture shows the target side cannot swallow the changes in a time fashion, the reasons maybe network bandwidth, target DB under heavy load, the table(s) has no PK etc.&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 01:00:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/CDC-Taking-Time/m-p/2481389#M12709</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2024-09-13T01:00:19Z</dc:date>
    </item>
  </channel>
</rss>

