<?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 Designing the Qlik data model in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Designing-the-Qlik-data-model/m-p/1315686#M28234</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was at Qlik Qonnections last week and attended &lt;A href="https://community.qlik.com/qlik-users/4003"&gt;hic&lt;/A&gt;‌ presentation on under the hood, which was a fantastic presentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It got me thinking about the Qlik data model design, my question is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'If it really necessary to design a dimensional model and load this data into Qlik? If I was to add the dimensions to the fact table and the resultant table was not too wide would this be a more efficient data model? How wide is considered too wide?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interested in everyone's thoughts on this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 May 2017 19:33:14 GMT</pubDate>
    <dc:creator>pschmidt1973</dc:creator>
    <dc:date>2017-05-22T19:33:14Z</dc:date>
    <item>
      <title>Designing the Qlik data model</title>
      <link>https://community.qlik.com/t5/App-Development/Designing-the-Qlik-data-model/m-p/1315686#M28234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was at Qlik Qonnections last week and attended &lt;A href="https://community.qlik.com/qlik-users/4003"&gt;hic&lt;/A&gt;‌ presentation on under the hood, which was a fantastic presentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It got me thinking about the Qlik data model design, my question is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'If it really necessary to design a dimensional model and load this data into Qlik? If I was to add the dimensions to the fact table and the resultant table was not too wide would this be a more efficient data model? How wide is considered too wide?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interested in everyone's thoughts on this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 19:33:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Designing-the-Qlik-data-model/m-p/1315686#M28234</guid>
      <dc:creator>pschmidt1973</dc:creator>
      <dc:date>2017-05-22T19:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: Designing the Qlik data model</title>
      <link>https://community.qlik.com/t5/App-Development/Designing-the-Qlik-data-model/m-p/1315687#M28235</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The star schema dimensional model provides a nice balance of RAM usage and runtime performance. A single flattened&amp;nbsp; table or even an extreme snowflake will produce the correct results. For typical small to medium apps any of the models will provide acceptable performance and resource usage. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In some cases a single table can provide better response time, but at the cost of significantly more RAM.&amp;nbsp; It's usually not worth the tradeoff in my experience. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Rob&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://masterssummit.com" rel="nofollow" target="_blank"&gt;http://masterssummit.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://qlikviewcookbook.com" rel="nofollow" target="_blank"&gt;http://qlikviewcookbook.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 22:25:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Designing-the-Qlik-data-model/m-p/1315687#M28235</guid>
      <dc:creator>rwunderlich</dc:creator>
      <dc:date>2017-05-22T22:25:22Z</dc:date>
    </item>
  </channel>
</rss>

