<?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: Application Stop Working in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Application-Stop-Working/m-p/1386940#M799651</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Huge amounts of data require either&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Huge amounts of RAM (but usually less of it)&lt;/LI&gt;&lt;LI&gt;Optimizations to reduce the memory footprint of your document.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Optimizations may include amongst others:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Aggregating away the detail rows in your script - managers often don't want to see the details, operational people need only specific operations details etc.&lt;/LI&gt;&lt;LI&gt;Reducing the complexity of your data model - a star of snowflake layout with a single facts table is preferred&lt;/LI&gt;&lt;LI&gt;Reducing cardinality (# of distinct values) in all fields&lt;/LI&gt;&lt;LI&gt;Splitting your document in functional units, business-wise.&lt;/LI&gt;&lt;LI&gt;Etc.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Nov 2017 11:15:43 GMT</pubDate>
    <dc:creator>Peter_Cammaert</dc:creator>
    <dc:date>2017-11-28T11:15:43Z</dc:date>
    <item>
      <title>Application Stop Working</title>
      <link>https://community.qlik.com/t5/QlikView/Application-Stop-Working/m-p/1386939#M799650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As my application contains huge amount of data,due to which it hangs up,does not work properly.So what is solution for it to work it proper ?&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/Application-Stop-Working/m-p/1386939#M799650</guid>
      <dc:creator>dhavalvyas</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Application Stop Working</title>
      <link>https://community.qlik.com/t5/QlikView/Application-Stop-Working/m-p/1386940#M799651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Huge amounts of data require either&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Huge amounts of RAM (but usually less of it)&lt;/LI&gt;&lt;LI&gt;Optimizations to reduce the memory footprint of your document.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Optimizations may include amongst others:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Aggregating away the detail rows in your script - managers often don't want to see the details, operational people need only specific operations details etc.&lt;/LI&gt;&lt;LI&gt;Reducing the complexity of your data model - a star of snowflake layout with a single facts table is preferred&lt;/LI&gt;&lt;LI&gt;Reducing cardinality (# of distinct values) in all fields&lt;/LI&gt;&lt;LI&gt;Splitting your document in functional units, business-wise.&lt;/LI&gt;&lt;LI&gt;Etc.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Nov 2017 11:15:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Application-Stop-Working/m-p/1386940#M799651</guid>
      <dc:creator>Peter_Cammaert</dc:creator>
      <dc:date>2017-11-28T11:15:43Z</dc:date>
    </item>
  </channel>
</rss>

