<?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: Choosing a right Data Model in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Choosing-a-right-Data-Model/m-p/510933#M190874</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you read this document already: &lt;A href="https://community.qlik.com/docs/DOC-3412"&gt;Joins and Lookups&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The pdf's in this discussion may help too: &lt;A href="https://community.qlik.com/message/427753"&gt;Re: Performance Optimisation and Multiple Fact Tables&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Nov 2013 17:28:04 GMT</pubDate>
    <dc:creator>Gysbert_Wassenaar</dc:creator>
    <dc:date>2013-11-29T17:28:04Z</dc:date>
    <item>
      <title>Choosing a right Data Model</title>
      <link>https://community.qlik.com/t5/QlikView/Choosing-a-right-Data-Model/m-p/510932#M190873</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;Can anyone help me in selecting the right data model. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Model 1. A Fact Table at the heart of the model and all dimensions connecting to it.&lt;/P&gt;&lt;P&gt;Model 2. A flattened Fact Table with most of the dimensions merged into it (wherever possible/feasible)&lt;/P&gt;&lt;P&gt;The second approach seems to give a more responsive UI. However is there any downside to it that I may have missed?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have attached an image to explain this. Please note that the image is just an example, the real model contains almost a hundred dimension tables and has millions of rows of data in the Fact table, and some of the dimension tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will appreciate if anyone can help me understand the advantages and disadvantages of both the approaches (keeping in mind the volume of data the model is supposed to hold).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bhaskar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Nov 2013 17:10:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Choosing-a-right-Data-Model/m-p/510932#M190873</guid>
      <dc:creator>bhaskarsharma03</dc:creator>
      <dc:date>2013-11-29T17:10:50Z</dc:date>
    </item>
    <item>
      <title>Re: Choosing a right Data Model</title>
      <link>https://community.qlik.com/t5/QlikView/Choosing-a-right-Data-Model/m-p/510933#M190874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you read this document already: &lt;A href="https://community.qlik.com/docs/DOC-3412"&gt;Joins and Lookups&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The pdf's in this discussion may help too: &lt;A href="https://community.qlik.com/message/427753"&gt;Re: Performance Optimisation and Multiple Fact Tables&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Nov 2013 17:28:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Choosing-a-right-Data-Model/m-p/510933#M190874</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2013-11-29T17:28:04Z</dc:date>
    </item>
  </channel>
</rss>

