<?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>article Qlik Replicate: No Insert happening on Azure Synapse SQL Pool in Bulk Mode in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-No-Insert-happening-on-Azure-Synapse-SQL-Pool-in/ta-p/2513456</link>
    <description>&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Azure Synapse&lt;/STRONG&gt;&lt;/FONT&gt; as the target may be affected by a defect that causes the endpoint to not correctly path the staging folder. Extra slashes (&lt;FONT face="courier new,courier"&gt;/&lt;/FONT&gt;) may be observed in file paths, leading to files not being loaded to the target correctly when Azure SQL copy commands are executed.&lt;/P&gt;
&lt;P&gt;No errors are logged or displayed and the staging files remain available in the correct folder. The only symptom of this issue is data not being replicated to the base tables.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Affected Versions&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;Qlik Replicate November 2024 SR1 (current) and all earlier versions.&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Fix Version&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;A patch will be released in the future to address this issue. Early build &lt;FONT color="#339966"&gt;&lt;STRONG&gt;2024.11.444&lt;/STRONG&gt;&lt;/FONT&gt; is being actively developed and can be requested using a Support case.&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Workaround&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;To mitigate the issue, use &lt;FONT color="#339966"&gt;&lt;STRONG&gt;ADLS Gen2&lt;/STRONG&gt;&lt;/FONT&gt; storage instead of &lt;STRONG&gt;&lt;FONT color="#339966"&gt;BLOB storage&lt;/FONT&gt;&lt;/STRONG&gt;. SUPPORT-1644 only impacts BLOB storage.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="azure data lake storage adls gen2.png" style="width: 664px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/179443i0B06C6A70DDBE1C1/image-dimensions/664x532?v=v2" width="664" height="532" role="button" title="azure data lake storage adls gen2.png" alt="azure data lake storage adls gen2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cause&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;This is caused by SUPPORT-1644, which leads to incorrect file paths between the staging folder locations and the copy commands executed by the task. Qlik is actively working on resolving the issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Internal Investigation ID(s)&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;SUPPORT-1644&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qik Replicate&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Tue, 08 Apr 2025 08:27:58 GMT</pubDate>
    <dc:creator>Alan_Wang</dc:creator>
    <dc:date>2025-04-08T08:27:58Z</dc:date>
    <item>
      <title>Qlik Replicate: No Insert happening on Azure Synapse SQL Pool in Bulk Mode</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-No-Insert-happening-on-Azure-Synapse-SQL-Pool-in/ta-p/2513456</link>
      <description>&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Azure Synapse&lt;/STRONG&gt;&lt;/FONT&gt; as the target may be affected by a defect that causes the endpoint to not correctly path the staging folder. Extra slashes (&lt;FONT face="courier new,courier"&gt;/&lt;/FONT&gt;) may be observed in file paths, leading to files not being loaded to the target correctly when Azure SQL copy commands are executed.&lt;/P&gt;
&lt;P&gt;No errors are logged or displayed and the staging files remain available in the correct folder. The only symptom of this issue is data not being replicated to the base tables.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Affected Versions&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;Qlik Replicate November 2024 SR1 (current) and all earlier versions.&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Fix Version&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;A patch will be released in the future to address this issue. Early build &lt;FONT color="#339966"&gt;&lt;STRONG&gt;2024.11.444&lt;/STRONG&gt;&lt;/FONT&gt; is being actively developed and can be requested using a Support case.&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Workaround&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;To mitigate the issue, use &lt;FONT color="#339966"&gt;&lt;STRONG&gt;ADLS Gen2&lt;/STRONG&gt;&lt;/FONT&gt; storage instead of &lt;STRONG&gt;&lt;FONT color="#339966"&gt;BLOB storage&lt;/FONT&gt;&lt;/STRONG&gt;. SUPPORT-1644 only impacts BLOB storage.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="azure data lake storage adls gen2.png" style="width: 664px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/179443i0B06C6A70DDBE1C1/image-dimensions/664x532?v=v2" width="664" height="532" role="button" title="azure data lake storage adls gen2.png" alt="azure data lake storage adls gen2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cause&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;This is caused by SUPPORT-1644, which leads to incorrect file paths between the staging folder locations and the copy commands executed by the task. Qlik is actively working on resolving the issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Internal Investigation ID(s)&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;SUPPORT-1644&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qik Replicate&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Tue, 08 Apr 2025 08:27:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-No-Insert-happening-on-Azure-Synapse-SQL-Pool-in/ta-p/2513456</guid>
      <dc:creator>Alan_Wang</dc:creator>
      <dc:date>2025-04-08T08:27:58Z</dc:date>
    </item>
  </channel>
</rss>

