<?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: SQL Server Transactional Replication - Updates Only in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/SQL-Server-Transactional-Replication-Updates-Only/m-p/2418495#M9453</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/152036"&gt;@Praveen_Devaram&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/121014"&gt;@Dana_Baldwin&lt;/a&gt;&amp;nbsp;'s solution works however I still want to understand further about the task design: if capture UPDATE only, then how about the INSERT records? if all the INSERT operations are ignored, the target UPDATE maybe failed as the INSERT row cannot replicated to target side, then the UPDATE operation cannot find the target row, unless the task set to UPSERT Mode, or Store Changes Mode. So far we still need replicate the INSERT and DELETE operations to make sure the data synchronization between source and target side.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;John.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Feb 2024 01:26:24 GMT</pubDate>
    <dc:creator>john_wang</dc:creator>
    <dc:date>2024-02-14T01:26:24Z</dc:date>
    <item>
      <title>SQL Server Transactional Replication - Updates Only</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/SQL-Server-Transactional-Replication-Updates-Only/m-p/2418487#M9450</link>
      <description>&lt;P&gt;With native SQL Server transactional replication, you can turn off insert/udpate/delete in the article properties &amp;gt; statement delivery section.&lt;/P&gt;
&lt;P&gt;Is there similar functionality with Qlik?&lt;/P&gt;
&lt;P&gt;I'd like to create a task where it will only capture updates for a specific table.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Praveen_Devaram_0-1707869065423.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/159682i5BD4CB864A2330B0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Praveen_Devaram_0-1707869065423.png" alt="Praveen_Devaram_0-1707869065423.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2024 00:05:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/SQL-Server-Transactional-Replication-Updates-Only/m-p/2418487#M9450</guid>
      <dc:creator>Praveen_Devaram</dc:creator>
      <dc:date>2024-02-14T00:05:34Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server Transactional Replication - Updates Only</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/SQL-Server-Transactional-Replication-Updates-Only/m-p/2418489#M9451</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/152036"&gt;@Praveen_Devaram&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This section in the user guide should help:&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/replicate/November2023/Content/Global_Common/Content/SharedEMReplicate/Customize%20Tasks/tasks_recordSelection.htm#ar_tasks_custom_1624443382_1761564" target="_blank"&gt;Creating a record selection condition for one or more columns #Creating a record selection condition for one or more columns | Qlik Replicate Help&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2024 00:18:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/SQL-Server-Transactional-Replication-Updates-Only/m-p/2418489#M9451</guid>
      <dc:creator>Dana_Baldwin</dc:creator>
      <dc:date>2024-02-14T00:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server Transactional Replication - Updates Only</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/SQL-Server-Transactional-Replication-Updates-Only/m-p/2418495#M9453</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/152036"&gt;@Praveen_Devaram&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/121014"&gt;@Dana_Baldwin&lt;/a&gt;&amp;nbsp;'s solution works however I still want to understand further about the task design: if capture UPDATE only, then how about the INSERT records? if all the INSERT operations are ignored, the target UPDATE maybe failed as the INSERT row cannot replicated to target side, then the UPDATE operation cannot find the target row, unless the task set to UPSERT Mode, or Store Changes Mode. So far we still need replicate the INSERT and DELETE operations to make sure the data synchronization between source and target side.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;John.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2024 01:26:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/SQL-Server-Transactional-Replication-Updates-Only/m-p/2418495#M9453</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2024-02-14T01:26:24Z</dc:date>
    </item>
  </channel>
</rss>

