<?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: What is Latching in Qlik replicate? in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1890014#M1819</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;With regards to the table mentioned by Hein,&lt;/P&gt;
&lt;P&gt;In SQL Server, We keep open 2 transaction as part of Replication. Please refer to the source table : attrep_truncation_safeguard&lt;/P&gt;
&lt;P&gt;There will be 2 rows per active task: A and B&lt;BR /&gt;Replicate opens a RW Transaction and selects one of the row, after 5 minutes (Endpoint config), it starts a TX for the other RX, updates the first row to the current time and commits. Thus there is always an open transaction.&lt;/P&gt;
&lt;P&gt;You should not run any maintenance against the attrep_truncation_safeguard table. If you cannot exclude this table from the maintenance plan, then you should stop the Replicate task during the maintenance window.&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR /&gt;Lyka&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 08 Feb 2022 01:04:44 GMT</pubDate>
    <dc:creator>lyka</dc:creator>
    <dc:date>2022-02-08T01:04:44Z</dc:date>
    <item>
      <title>What is Latching in Qlik replicate?</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1889962#M1815</link>
      <description>&lt;P&gt;what is latching in the Qlik replicate.&amp;nbsp; At the sql server db side, they are facing high OS paging issues. What should be done at this time at the Qlik replicate side.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Feb 2022 21:10:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1889962#M1815</guid>
      <dc:creator>suvbin</dc:creator>
      <dc:date>2022-02-07T21:10:29Z</dc:date>
    </item>
    <item>
      <title>Re: What is Latching in Qlik replicate?</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1890014#M1819</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;With regards to the table mentioned by Hein,&lt;/P&gt;
&lt;P&gt;In SQL Server, We keep open 2 transaction as part of Replication. Please refer to the source table : attrep_truncation_safeguard&lt;/P&gt;
&lt;P&gt;There will be 2 rows per active task: A and B&lt;BR /&gt;Replicate opens a RW Transaction and selects one of the row, after 5 minutes (Endpoint config), it starts a TX for the other RX, updates the first row to the current time and commits. Thus there is always an open transaction.&lt;/P&gt;
&lt;P&gt;You should not run any maintenance against the attrep_truncation_safeguard table. If you cannot exclude this table from the maintenance plan, then you should stop the Replicate task during the maintenance window.&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR /&gt;Lyka&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Feb 2022 01:04:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1890014#M1819</guid>
      <dc:creator>lyka</dc:creator>
      <dc:date>2022-02-08T01:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: What is Latching in Qlik replicate?</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1890623#M1821</link>
      <description>&lt;P&gt;Where can i find this "&lt;SPAN&gt;&amp;nbsp;attrep_truncation_safeguard" ? in the source db?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Feb 2022 20:20:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1890623#M1821</guid>
      <dc:creator>suvbin</dc:creator>
      <dc:date>2022-02-08T20:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: What is Latching in Qlik replicate?</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1890624#M1822</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt;&amp;nbsp;&lt;SPAN&gt;Where can i find this "&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;attrep_truncation_safeguard" ? in the source db?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;DONT. Not now, not yet.&lt;/P&gt;
&lt;P&gt;First Tell us what YOU KNOW. What you see, why you are asked the main questions in the first place.&lt;/P&gt;
&lt;P&gt;Right now, for me, your main question is similar to 'my car makes a funny sound, how do I change the trailer?' Followed by 'where is the caliper?'.&lt;/P&gt;
&lt;P&gt;Try to restate you question. Help us help you.&lt;/P&gt;
&lt;P&gt;Hein.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Feb 2022 20:35:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1890624#M1822</guid>
      <dc:creator>Heinvandenheuvel</dc:creator>
      <dc:date>2022-02-08T20:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: What is Latching in Qlik replicate?</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1894019#M1872</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;
&lt;P&gt;Its in the source database&amp;nbsp; - if you are referring to the latch in SQL server.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Lyka&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 00:00:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/What-is-Latching-in-Qlik-replicate/m-p/1894019#M1872</guid>
      <dc:creator>lyka</dc:creator>
      <dc:date>2022-02-17T00:00:11Z</dc:date>
    </item>
  </channel>
</rss>

