<?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: QlikView data volume in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076838#M923687</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you very much to everyone for your answers.The idea of transforming the data to save space and time is very good and innovative, I did not know this before.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Apr 2016 09:40:56 GMT</pubDate>
    <dc:creator />
    <dc:date>2016-04-08T09:40:56Z</dc:date>
    <item>
      <title>QlikView data volume</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076834#M923683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: black;"&gt;Hi good afternoon everyone, I have a question regarding the volume of data that can work QlikView.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: black;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: black;"&gt;The question is this if I have a fact table 12 fields with 600 million records and five dimension tables, where each has two fields and contain 56 million records QlikView can handle this volume of data to generate reports without problems? and in the case that&amp;nbsp; time may take more or less time to load this information into the memory of server?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: black;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: black;"&gt;Thank you very much!!!&lt;/SPAN&gt;&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/QlikView-data-volume/m-p/1076834#M923683</guid>
      <dc:creator />
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView data volume</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076835#M923684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If your dimension tables only have two fields consider using &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;mapping tables with applymap to create a single table data model. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With large tables like this look at using an incremental load to improve load performance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 19:21:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076835#M923684</guid>
      <dc:creator>Colin-Albert</dc:creator>
      <dc:date>2016-04-07T19:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView data volume</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076836#M923685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A very important point by large datasets is the cardinality of the data, see: &lt;A href="https://community.qlik.com/qlik-blogpost/3632"&gt;The Importance Of Being Distinct&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2016 05:43:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076836#M923685</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2016-04-08T05:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView data volume</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076837#M923686</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Some organisations use Qlikview on terabytes sized source tables. With enough ram Qlikview can handle your data. Do look into using mapping tables to merge the values from your dimension tables into the fact table as &lt;A _jive_internal="true" href="https://community.qlik.com/people/colin_albert"&gt;Colin Albert&lt;/A&gt; says. And read the blog post &lt;A _jive_internal="true" href="https://community.qlik.com/people/Marcus_Sommer"&gt;Marcus&lt;/A&gt; referred to. If you have a datetime/timestamp fields you can probably split them in date and time fields and save space and time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2016 06:01:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076837#M923686</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2016-04-08T06:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView data volume</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076838#M923687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you very much to everyone for your answers.The idea of transforming the data to save space and time is very good and innovative, I did not know this before.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2016 09:40:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-data-volume/m-p/1076838#M923687</guid>
      <dc:creator />
      <dc:date>2016-04-08T09:40:56Z</dc:date>
    </item>
  </channel>
</rss>

