<?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: Problems with data model and dashboard loading  due to HUGE DATA. in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Problems-with-data-model-and-dashboard-loading-due-to-HUGE-DATA/m-p/1515206#M748578</link>
    <description>&lt;P&gt;There might be a lot of keys to success:&lt;/P&gt;&lt;P&gt;1. Aggregated data. Try using correct data granularity. Might business would be grateful for monthly, weekly data, not daily or even hourly.&lt;/P&gt;&lt;P&gt;2. Save space by reducing unnecessary fields, use Autonumberhash256 for keys as they tend to eat a lot of space.&lt;/P&gt;&lt;P&gt;3. Split fields like timestamps, names surnames, address, phone number or other long strings/numbers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no fast way to do this. The application optimization is the key.&lt;/P&gt;</description>
    <pubDate>Sat, 01 Dec 2018 20:31:37 GMT</pubDate>
    <dc:creator>MindaugasBacius</dc:creator>
    <dc:date>2018-12-01T20:31:37Z</dc:date>
    <item>
      <title>Problems with data model and dashboard loading  due to HUGE DATA.</title>
      <link>https://community.qlik.com/t5/QlikView/Problems-with-data-model-and-dashboard-loading-due-to-HUGE-DATA/m-p/1515204#M748577</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a table which has Around 44 Crores (i.e 440 Million records) per month.(distinct&amp;nbsp; records&amp;nbsp; )&amp;nbsp;&lt;/P&gt;&lt;P&gt;So we decide to create Qvd's by month...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After doing so many Joins and calculations&amp;nbsp; (Much required columns which we want to use them in&amp;nbsp; dashboard for set analysis or for list boxes etc etc)&lt;/P&gt;&lt;P&gt;So we can't ignore these columns (these has to be calculated in Data model itself)&lt;/P&gt;&lt;P&gt;I have optimised the QVD (row based optimisation)&lt;/P&gt;&lt;P&gt;Its taking atleast 2hrs to execute the Datamodel (sometimes even the system might get hanged , u can see black out screens )&lt;/P&gt;&lt;P&gt;Just to load 3 months Data..!&lt;/P&gt;&lt;P&gt;After all the joins and Filters required data is coming to 8 crore records (80 millions records)&lt;/P&gt;&lt;P&gt;Data model size is going upto 5GB&lt;/P&gt;&lt;P&gt;Which is making DASHBOARD TO LOAD SLOW AND EVEN GETTING IT STRUCKED...&lt;/P&gt;&lt;P&gt;i even tried to Break the data model into two parts (one with data cleansing)&amp;nbsp; which has raw data&lt;/P&gt;&lt;P&gt;Which stores in single QVD&lt;/P&gt;&lt;P&gt;And from that QVD (80 million records) I'm making certain Columns which are mandatory (as said above)&lt;/P&gt;&lt;P&gt;Still I'm facing the same issue......!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;IS there a way to execute this Datamodel to run fast.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or atleast DASHBOARD to react quickly (no hangs etc,) to respond quickly ???&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 21:47:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Problems-with-data-model-and-dashboard-loading-due-to-HUGE-DATA/m-p/1515204#M748577</guid>
      <dc:creator>SK28</dc:creator>
      <dc:date>2024-11-16T21:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with data model and dashboard loading  due to HUGE DATA.</title>
      <link>https://community.qlik.com/t5/QlikView/Problems-with-data-model-and-dashboard-loading-due-to-HUGE-DATA/m-p/1515206#M748578</link>
      <description>&lt;P&gt;There might be a lot of keys to success:&lt;/P&gt;&lt;P&gt;1. Aggregated data. Try using correct data granularity. Might business would be grateful for monthly, weekly data, not daily or even hourly.&lt;/P&gt;&lt;P&gt;2. Save space by reducing unnecessary fields, use Autonumberhash256 for keys as they tend to eat a lot of space.&lt;/P&gt;&lt;P&gt;3. Split fields like timestamps, names surnames, address, phone number or other long strings/numbers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no fast way to do this. The application optimization is the key.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Dec 2018 20:31:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Problems-with-data-model-and-dashboard-loading-due-to-HUGE-DATA/m-p/1515206#M748578</guid>
      <dc:creator>MindaugasBacius</dc:creator>
      <dc:date>2018-12-01T20:31:37Z</dc:date>
    </item>
  </channel>
</rss>

