<?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 Optimizing Data Reload Performance in Move to Qlik Cloud Analytics</title>
    <link>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510610#M2523</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need to reload a table daily that contains 60 million rows and 125 columns. I considered an incremental reload, but it doesn’t seem feasible since this is a snapshot of the previous day's stock levels.&lt;/P&gt;&lt;P&gt;Do you have any recommendations to speed up this reload on &lt;LI-PRODUCT title="Qlik Cloud" id="qlikSenseEnterpriseSaaS"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;? Previously, we performed this operation on &lt;LI-PRODUCT title="QlikView" id="qlikView"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;, where the loading times were significantly shorter.&lt;/P&gt;&lt;P&gt;Thank you in advance for your help.&lt;BR /&gt;&lt;BR /&gt;Enjoy your Qlik.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;Théo ATRAGIE.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jan 2026 10:45:26 GMT</pubDate>
    <dc:creator>theoat</dc:creator>
    <dc:date>2026-01-27T10:45:26Z</dc:date>
    <item>
      <title>Optimizing Data Reload Performance</title>
      <link>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510610#M2523</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need to reload a table daily that contains 60 million rows and 125 columns. I considered an incremental reload, but it doesn’t seem feasible since this is a snapshot of the previous day's stock levels.&lt;/P&gt;&lt;P&gt;Do you have any recommendations to speed up this reload on &lt;LI-PRODUCT title="Qlik Cloud" id="qlikSenseEnterpriseSaaS"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;? Previously, we performed this operation on &lt;LI-PRODUCT title="QlikView" id="qlikView"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;, where the loading times were significantly shorter.&lt;/P&gt;&lt;P&gt;Thank you in advance for your help.&lt;BR /&gt;&lt;BR /&gt;Enjoy your Qlik.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;Théo ATRAGIE.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 10:45:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510610#M2523</guid>
      <dc:creator>theoat</dc:creator>
      <dc:date>2026-01-27T10:45:26Z</dc:date>
    </item>
    <item>
      <title>Re: Optimizing Data Reload Performance</title>
      <link>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510629#M2524</link>
      <description>&lt;P&gt;Hi, do you really need all 125 columns? Retrieveing only the needed columns may reduce load times.&lt;/P&gt;&lt;P&gt;And the 60 millions rows is for the last day or it has historical data?&lt;/P&gt;&lt;P&gt;Also stocks with zero units exists on the table?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 08:25:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510629#M2524</guid>
      <dc:creator>rubenmarin</dc:creator>
      <dc:date>2025-03-19T08:25:53Z</dc:date>
    </item>
    <item>
      <title>Re: Optimizing Data Reload Performance</title>
      <link>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510663#M2526</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/249886"&gt;@theoat&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;For large Data Sets I use a mix of Incremental Load and Data Partition. Since Incremental Load is not an option you could try Data Partition. The concept is simple. You pick a field (or fields) from your data set that does not change over time and that makes sense to group by. Often, I group my data by Year/Month. My QVDs/Parquets will look like:&lt;/P&gt;&lt;P&gt;...&lt;BR /&gt;stock_202412.qvd&lt;BR /&gt;stock_202501.qvd&lt;BR /&gt;stock_202502.qvd&lt;BR /&gt;stock_202503.qvd&lt;BR /&gt;...&lt;/P&gt;&lt;P&gt;You can even create a logic where you only process the current month plus the previous X months reducing drastically the extraction times.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Mark Costa&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 12:38:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510663#M2526</guid>
      <dc:creator>marksouzacosta</dc:creator>
      <dc:date>2025-03-19T12:38:53Z</dc:date>
    </item>
    <item>
      <title>Re: Optimizing Data Reload Performance</title>
      <link>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510699#M2527</link>
      <description>&lt;P&gt;To add to what&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/22035"&gt;@marksouzacosta&lt;/a&gt;&amp;nbsp;suggested, here's an article on segmenting QVDs with some code samples.&lt;/P&gt;&lt;P&gt;&lt;A href="https://qlikviewcookbook.com/2022/03/how-to-segment-qvd-files/" target="_blank"&gt;https://qlikviewcookbook.com/2022/03/how-to-segment-qvd-files/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;-Rob&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 15:20:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Move-to-Qlik-Cloud-Analytics/Optimizing-Data-Reload-Performance/m-p/2510699#M2527</guid>
      <dc:creator>rwunderlich</dc:creator>
      <dc:date>2025-03-19T15:20:28Z</dc:date>
    </item>
  </channel>
</rss>

