<?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 Best Practice: Loading QVD files in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Best-Practice-Loading-QVD-files/ta-p/1712909</link>
    <description>&lt;P&gt;QlikView Data (QVD) file is a optimized file format for storing QlikView data tables. The file has a binary data format that can be loaded directly to computer memory without any processing required, which makes it the fastest way to load data into a QlikView application. This way of directly loading data into memory is referred to as an optimized load.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In QlikView desktop client this optimized load is indicated by the "Script Execution Progress" dialog showing "qvd optimized" when the QVD file is loaded into memory.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Script Execution Progress QVD optimized.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/56552iB2FCBC0BE035FF48/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Script Execution Progress QVD optimized.png" alt="Script Execution Progress QVD optimized.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;If changes are made to the data or table structure during reload the load will no longer be optimized. In this scenario there is no longer a reference to "qvd optimized" in the&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Script Execution Progress.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/56553i23B7AE36EF878DE1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Script Execution Progress.png" alt="Script Execution Progress.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;The recommended approach for loading QVD file is to always ensure they are loaded as optimized. If changes are required in the loaded data, then this should be applied through the resident load. This could be done by the principle below, where an optimized load is done to a temporary table which is later dropped.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;TmpTable:
LOAD *
FROM MyDatya.qvd (QVD);

MyTable:
LOAD 
  *, Today() AS TodaysDate
RESIDENT TmpTable;

DROP Table TmpTable;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Environment:&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="QlikView" id="qlikView"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;BR /&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 09 Jun 2021 14:30:04 GMT</pubDate>
    <dc:creator>ToniKautto</dc:creator>
    <dc:date>2021-06-09T14:30:04Z</dc:date>
    <item>
      <title>Best Practice: Loading QVD files</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Best-Practice-Loading-QVD-files/ta-p/1712909</link>
      <description>&lt;P&gt;QlikView Data (QVD) file is a optimized file format for storing QlikView data tables. The file has a binary data format that can be loaded directly to computer memory without any processing required, which makes it the fastest way to load data into a QlikView application. This way of directly loading data into memory is referred to as an optimized load.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In QlikView desktop client this optimized load is indicated by the "Script Execution Progress" dialog showing "qvd optimized" when the QVD file is loaded into memory.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Script Execution Progress QVD optimized.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/56552iB2FCBC0BE035FF48/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Script Execution Progress QVD optimized.png" alt="Script Execution Progress QVD optimized.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;If changes are made to the data or table structure during reload the load will no longer be optimized. In this scenario there is no longer a reference to "qvd optimized" in the&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Script Execution Progress.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/56553i23B7AE36EF878DE1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Script Execution Progress.png" alt="Script Execution Progress.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;The recommended approach for loading QVD file is to always ensure they are loaded as optimized. If changes are required in the loaded data, then this should be applied through the resident load. This could be done by the principle below, where an optimized load is done to a temporary table which is later dropped.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;TmpTable:
LOAD *
FROM MyDatya.qvd (QVD);

MyTable:
LOAD 
  *, Today() AS TodaysDate
RESIDENT TmpTable;

DROP Table TmpTable;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Environment:&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="QlikView" id="qlikView"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;BR /&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jun 2021 14:30:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Best-Practice-Loading-QVD-files/ta-p/1712909</guid>
      <dc:creator>ToniKautto</dc:creator>
      <dc:date>2021-06-09T14:30:04Z</dc:date>
    </item>
  </channel>
</rss>

