<?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: Inmemory in Qv in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Inmemory-in-Qv/m-p/604123#M1118979</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;When you are accessing Dashboard using AccessPoint or Desktop the entire dashboard data is stored in RAM and then when you change any selections it generates the charts using data in RAM instead of fetching from File System or database.&amp;nbsp; So, that is why you are getting faster results.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;traditional bi tools like cognos or Bo fetches the data from disks but qlikview opposes that is the why performance is increased.&lt;A href="https://community.qlik.com/message/441255"&gt;Inmemory,&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px; line-height: 1.5em;"&gt;chek the thread.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt; regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;Mahesh T&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Feb 2014 09:48:27 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-02-04T09:48:27Z</dc:date>
    <item>
      <title>Inmemory in Qv</title>
      <link>https://community.qlik.com/t5/QlikView/Inmemory-in-Qv/m-p/604122#M1118978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #ff00ff; font-size: 14pt;"&gt;&lt;STRONG&gt;Hi,&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff00ff; font-size: 14pt;"&gt;&lt;STRONG&gt;I want to know about inmemory and how it works in QV...?&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Feb 2014 09:45:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Inmemory-in-Qv/m-p/604122#M1118978</guid>
      <dc:creator />
      <dc:date>2014-02-04T09:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: Inmemory in Qv</title>
      <link>https://community.qlik.com/t5/QlikView/Inmemory-in-Qv/m-p/604123#M1118979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;When you are accessing Dashboard using AccessPoint or Desktop the entire dashboard data is stored in RAM and then when you change any selections it generates the charts using data in RAM instead of fetching from File System or database.&amp;nbsp; So, that is why you are getting faster results.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;traditional bi tools like cognos or Bo fetches the data from disks but qlikview opposes that is the why performance is increased.&lt;A href="https://community.qlik.com/message/441255"&gt;Inmemory,&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px; line-height: 1.5em;"&gt;chek the thread.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt; regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12.727272033691406px;"&gt;Mahesh T&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Feb 2014 09:48:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Inmemory-in-Qv/m-p/604123#M1118979</guid>
      <dc:creator />
      <dc:date>2014-02-04T09:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: Inmemory in Qv</title>
      <link>https://community.qlik.com/t5/QlikView/Inmemory-in-Qv/m-p/604124#M1118980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See this blog post: &lt;A _jive_internal="true" class="j-search-result-value" href="https://community.qlik.com/blogs/qlikviewdesignblog/2012/11/20/symbol-tables-and-bit-stuffed-pointers" style="margin: 0 0 3px; font-weight: bold; font-size: 15px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3778c7;"&gt;Symbol Tables and Bit-Stuffed Pointers&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Feb 2014 09:48:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Inmemory-in-Qv/m-p/604124#M1118980</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2014-02-04T09:48:31Z</dc:date>
    </item>
  </channel>
</rss>

