<?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 Regarding External Tables and Temporary Tables with Azure Synapse Analytics as the Target in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551705#M16448</link>
    <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Hi, all.&lt;/P&gt;&lt;P&gt;In Qlik Replicate, when targeting Azure Synapse Analytics, the data processing flow appears to operate as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Uploading CSV files to storage&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Creating an external table based on the CSV files&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Performing a COPY INTO operation from the external table into a temporary table&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Joining the temporary table with the target table to execute a bulk UPDATE/DELETE&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Regarding this workflow, I have a question about the design: If we were to join the external table directly with the target table instead of using a temporary table, we could skip the COPY INTO process entirely. I assume this would be faster and more efficient.&lt;/P&gt;&lt;P&gt;Could you please explain the reason why Qlik Replicate is implemented to follow this specific flow?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best&amp;nbsp;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 19 Jun 2026 07:40:02 GMT</pubDate>
    <dc:creator>iti-attunity-sup</dc:creator>
    <dc:date>2026-06-19T07:40:02Z</dc:date>
    <item>
      <title>Regarding External Tables and Temporary Tables with Azure Synapse Analytics as the Target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551705#M16448</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Hi, all.&lt;/P&gt;&lt;P&gt;In Qlik Replicate, when targeting Azure Synapse Analytics, the data processing flow appears to operate as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Uploading CSV files to storage&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Creating an external table based on the CSV files&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Performing a COPY INTO operation from the external table into a temporary table&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Joining the temporary table with the target table to execute a bulk UPDATE/DELETE&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Regarding this workflow, I have a question about the design: If we were to join the external table directly with the target table instead of using a temporary table, we could skip the COPY INTO process entirely. I assume this would be faster and more efficient.&lt;/P&gt;&lt;P&gt;Could you please explain the reason why Qlik Replicate is implemented to follow this specific flow?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best&amp;nbsp;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 19 Jun 2026 07:40:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551705#M16448</guid>
      <dc:creator>iti-attunity-sup</dc:creator>
      <dc:date>2026-06-19T07:40:02Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding External Tables and Temporary Tables with Azure Synapse Analytics as the Target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551730#M16453</link>
      <description>&lt;P&gt;Hello iti-attunity-sup,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for reaching out to the &lt;STRONG&gt;Qlik community&lt;/STRONG&gt;.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Qlik Replicate uses &lt;STRONG&gt;external table → COPY INTO → temp table → MERGE&lt;/STRONG&gt; because:&lt;/P&gt;
&lt;UL&gt;
 &lt;LI&gt;&lt;STRONG&gt;External tables are &lt;/STRONG&gt;&lt;A href="https://stackoverflow.com/questions/66608701/external-table-in-azure-synapse-very-slow-performance" target="_blank"&gt;&lt;STRONG&gt;slow for joins and DML&lt;/STRONG&gt;&lt;/A&gt; in Synapse.&amp;nbsp;&lt;/LI&gt;
 &lt;LI&gt;&lt;STRONG&gt;Microsoft &lt;/STRONG&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/synapse-analytics/sql/data-loading-best-practices" target="_blank"&gt;&lt;STRONG&gt;recommends &lt;/STRONG&gt;&lt;/A&gt;&lt;STRONG&gt;loading into staging/temp tables first&lt;/STRONG&gt; for best MPP performance.&amp;nbsp;&lt;/LI&gt;
 &lt;LI&gt;&lt;A href="https://learn.microsoft.com/en-us/sql/t-sql/statements/copy-into-transact-sql?view=azure-sqldw-latest" target="_blank"&gt;&lt;STRONG&gt;COPY INTO&lt;/STRONG&gt;&lt;/A&gt;&lt;STRONG&gt; is optimized for high‑throughput ingestion&lt;/STRONG&gt; into native tables.&lt;/LI&gt;
 &lt;LI&gt;&lt;STRONG&gt;Temp tables enable fast, set‑based &lt;/STRONG&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Replicate/Replicate-table-creation-quot-public-quot-quot-attrep/td-p/1786523" target="_blank"&gt;&lt;STRONG&gt;CDC updates/deletes&lt;/STRONG&gt;&lt;/A&gt; instead of row‑by‑row operations.&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Joining the external table directly would usually be &lt;STRONG&gt;slower and less scalable&lt;/STRONG&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jun 2026 12:44:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551730#M16453</guid>
      <dc:creator>Rahul_Kale</dc:creator>
      <dc:date>2026-06-19T12:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding External Tables and Temporary Tables with Azure Synapse Analytics as the Target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551819#M16459</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;SPAN&gt;Rahul_Kale-san.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;I now understand that external tables have a disadvantage in terms of speed, and that using temporary tables resolves this issue.&lt;BR /&gt;Thank you again for providing this very important information.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 04:41:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551819#M16459</guid>
      <dc:creator>iti-attunity-sup</dc:creator>
      <dc:date>2026-06-22T04:41:15Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding External Tables and Temporary Tables with Azure Synapse Analytics as the Target</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551838#M16460</link>
      <description>&lt;P&gt;Happy to help &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/142280"&gt;@iti-attunity-sup&lt;/a&gt;&lt;/SPAN&gt;.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 12:09:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Regarding-External-Tables-and-Temporary-Tables-with-Azure/m-p/2551838#M16460</guid>
      <dc:creator>Rahul_Kale</dc:creator>
      <dc:date>2026-06-22T12:09:16Z</dc:date>
    </item>
  </channel>
</rss>

