<?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 Qlik-Snowflake behaviour in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Snowflake-behaviour/m-p/2536512#M15492</link>
    <description>&lt;P&gt;Qlik Replicate performs frequent short metadata operations in the background—such as SHOW commands and similar lightweight queries. Snowflake documentation indicates that repeated short queries can contribute to higher credit consumption, especially when multiple threads or tasks are involved.&lt;/P&gt;
&lt;P data-start="368" data-end="609"&gt;Is there any way to reduce or control this behavior in Replicate?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Nov 2025 01:21:11 GMT</pubDate>
    <dc:creator>Sukanya2</dc:creator>
    <dc:date>2025-11-19T01:21:11Z</dc:date>
    <item>
      <title>Qlik-Snowflake behaviour</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Snowflake-behaviour/m-p/2536512#M15492</link>
      <description>&lt;P&gt;Qlik Replicate performs frequent short metadata operations in the background—such as SHOW commands and similar lightweight queries. Snowflake documentation indicates that repeated short queries can contribute to higher credit consumption, especially when multiple threads or tasks are involved.&lt;/P&gt;
&lt;P data-start="368" data-end="609"&gt;Is there any way to reduce or control this behavior in Replicate?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 01:21:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Snowflake-behaviour/m-p/2536512#M15492</guid>
      <dc:creator>Sukanya2</dc:creator>
      <dc:date>2025-11-19T01:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik-Snowflake behaviour</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Snowflake-behaviour/m-p/2536625#M15498</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/349997"&gt;@Sukanya2&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P data-start="82" data-end="229"&gt;Yes, Qlik Replicate uses &lt;STRONG data-start="107" data-end="122"&gt;SHOW TABLES&lt;/STRONG&gt; and &lt;STRONG data-start="127" data-end="143"&gt;SHOW SCHEMAS&lt;/STRONG&gt; to verify the existence of target tables. These operations are expected and required.&lt;/P&gt;
&lt;P data-start="231" data-end="524"&gt;If you believe the &lt;STRONG&gt;SHOW&lt;/STRONG&gt; commands are being executed unexpectedly, please open a support ticket. Make sure to set &lt;STRONG data-start="344" data-end="376"&gt;SOURCE_UNLOAD/SOURCE_CAPTURE&lt;/STRONG&gt; to &lt;EM data-start="380" data-end="389"&gt;Verbose&lt;/EM&gt;, and attach both the verbose task logs and the Diagnostics Package. Our support team will review the behavior and confirm it with R&amp;amp;D.&lt;/P&gt;
&lt;P data-start="231" data-end="524"&gt;Hope this helps.&lt;/P&gt;
&lt;P data-start="231" data-end="524"&gt;John.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 14:00:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Snowflake-behaviour/m-p/2536625#M15498</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2025-11-19T14:00:18Z</dc:date>
    </item>
  </channel>
</rss>

