<?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 Re: QVD Doudt in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4747#M791310</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The main advantage with a QVD file is that you can load it faster than any other data type. In addition, it is a fairly compact format, so that the size of it on disk is reasonably small.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, just as &lt;A href="https://community.qlik.com/qlik-users/13229"&gt;jontydkpi&lt;/A&gt;‌ points out, it does &lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;not&lt;/EM&gt;&lt;/SPAN&gt; affect the memory footprint of the app or the size of the qvw/qvf file. It will &lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;not&lt;/EM&gt;&lt;/SPAN&gt; reduce its size.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, there is no need to convert an existing text file to qvd - unless you need to load it fast. And there is no need to create a qvd if you have a good database connection - unless you need to load the table fast.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Jan 2018 15:49:20 GMT</pubDate>
    <dc:creator>hic</dc:creator>
    <dc:date>2018-01-22T15:49:20Z</dc:date>
    <item>
      <title>QVD Doudt</title>
      <link>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4743#M791306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In case we are using Other than QVD files as a source,Qlikview have as in memory capability (or) only we have QVD file need to create for inmemory&amp;nbsp; capability?&lt;/P&gt;&lt;P&gt;Pleas suggest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Raj.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4743#M791306</guid>
      <dc:creator>rajendras</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: QVD Doudt</title>
      <link>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4744#M791307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am not quite sure what you are asking, but the source file (QVD or other) makes no difference to the loaded QVW document which will always be in memory.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 12:48:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4744#M791307</guid>
      <dc:creator>jonathandienst</dc:creator>
      <dc:date>2018-01-22T12:48:28Z</dc:date>
    </item>
    <item>
      <title>Re: QVD Doudt</title>
      <link>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4745#M791308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your understand is correct, The only correction i am thinking is QVD get reduced some file size and memory which are stored in Inline storage. So, I would suggest you to use always QVD only &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 13:33:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4745#M791308</guid>
      <dc:creator>Anil_Babu_Samineni</dc:creator>
      <dc:date>2018-01-22T13:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: QVD Doudt</title>
      <link>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4746#M791309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;QVD will reduce your data upto 10% i believe, so it is best to use.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 13:48:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4746#M791309</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2018-01-22T13:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: QVD Doudt</title>
      <link>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4747#M791310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The main advantage with a QVD file is that you can load it faster than any other data type. In addition, it is a fairly compact format, so that the size of it on disk is reasonably small.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, just as &lt;A href="https://community.qlik.com/qlik-users/13229"&gt;jontydkpi&lt;/A&gt;‌ points out, it does &lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;not&lt;/EM&gt;&lt;/SPAN&gt; affect the memory footprint of the app or the size of the qvw/qvf file. It will &lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;not&lt;/EM&gt;&lt;/SPAN&gt; reduce its size.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, there is no need to convert an existing text file to qvd - unless you need to load it fast. And there is no need to create a qvd if you have a good database connection - unless you need to load the table fast.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 15:49:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QVD-Doudt/m-p/4747#M791310</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2018-01-22T15:49:20Z</dc:date>
    </item>
  </channel>
</rss>

