<?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 Re: Optimize performance configuration in Replicate task in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Optimize-performance-configuration-in-Replicate-task/m-p/2545765#M16095</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/132009"&gt;@Rueda&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;The DELETE operation generally takes longer to process because the system must search for the specific record before deleting it. You can enable VERBOSE logging on TARGET_APPLY to measure how long each DML statement takes to execute, which can help in assessing performance on the Azure database. I also observed that you are using ‘Transactional apply’ mode. In general, the performance of ‘Batch optimized apply’ mode is better than ‘Transactional apply’ mode.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Desmond&lt;/P&gt;</description>
    <pubDate>Mon, 30 Mar 2026 03:09:00 GMT</pubDate>
    <dc:creator>DesmondWOO</dc:creator>
    <dc:date>2026-03-30T03:09:00Z</dc:date>
    <item>
      <title>Optimize performance configuration in Replicate task</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Optimize-performance-configuration-in-Replicate-task/m-p/2545520#M16089</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I have a DB2 Z/OS source point and an end point which is an Azure SQL database with 12 cores. The virtual machine on which the Qlik Replicate server runs has 64GB of RAM and premium SSDs.&lt;BR /&gt;When delete operations are performed on the mainframe, I experience a significant delay in the deletion of records in Azure SQL.&lt;/P&gt;&lt;P&gt;Is this configuration correct?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Configuration_Tasks.png" style="width: 738px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/187453i5982B09D6248F3CA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Configuration_Tasks.png" alt="Configuration_Tasks.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Can we optimize this? can you suggest a configuration?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2026 11:06:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Optimize-performance-configuration-in-Replicate-task/m-p/2545520#M16089</guid>
      <dc:creator>Rueda</dc:creator>
      <dc:date>2026-03-26T11:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: Optimize performance configuration in Replicate task</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Optimize-performance-configuration-in-Replicate-task/m-p/2545765#M16095</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/132009"&gt;@Rueda&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;The DELETE operation generally takes longer to process because the system must search for the specific record before deleting it. You can enable VERBOSE logging on TARGET_APPLY to measure how long each DML statement takes to execute, which can help in assessing performance on the Azure database. I also observed that you are using ‘Transactional apply’ mode. In general, the performance of ‘Batch optimized apply’ mode is better than ‘Transactional apply’ mode.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Desmond&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 03:09:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Optimize-performance-configuration-in-Replicate-task/m-p/2545765#M16095</guid>
      <dc:creator>DesmondWOO</dc:creator>
      <dc:date>2026-03-30T03:09:00Z</dc:date>
    </item>
  </channel>
</rss>

