<?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: Star-Scheme always best method? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Star-Scheme-always-best-method/m-p/1529769#M438680</link>
    <description>&lt;P&gt;I would not agree with the statement that a Star Schema is always best for Qlik.&amp;nbsp; It depends on how you want the model to behave and what problem you are trying to solve.&lt;/P&gt;&lt;P&gt;In a typical database system, storing the Country field in a separate table would be most efficient for storage as it would eliminate redundant entries.&amp;nbsp; Qlik stores data differently, so this redundancy issue is lessened or non-existent in some cases.&amp;nbsp;&lt;/P&gt;&lt;P&gt;A star schema &lt;EM&gt;generally&lt;/EM&gt; provides the best balance of&amp;nbsp; storage and CPU usage at runtime.&amp;nbsp; However, I would argue that in many cases, it's not worth spending time getting to a star.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My first rule is code for clarity and simplicity.&amp;nbsp; Make the model easy to understand and use, and minimize the time you spend on creating and maintaining the script.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Considering your example.&amp;nbsp; The separate&amp;nbsp; Customer and Company tables are likely the way the data exists in your source system.&amp;nbsp; Keeping it the same is easy to write the script and understand the model.&amp;nbsp; What if I want a count of countries that purchased each product?&amp;nbsp; Count(Country); easy.&amp;nbsp; If I join Company to Customer I have to change to Count(DISTINCT Country); more complex.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We &lt;EM&gt;may&lt;/EM&gt; be able to say that reducing the number of "hops" in a data model by going from snowflake to star would improve chart calc time by about 10%.&amp;nbsp; If a chart now takes 50 milliseconds to calc and we reduce it to 45, is that important?&amp;nbsp; Was it worth the effort?&amp;nbsp; If I have 50 daily users with 30 clicks each, it it probably not significant.&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Rob&lt;BR /&gt;&lt;A href="http://masterssummit.com" target="_blank"&gt;http://masterssummit.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://qlikviewcookbook.com" target="_blank"&gt;http://qlikviewcookbook.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.easyqlik.com" target="_blank"&gt;http://www.easyqlik.com&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 14 Jan 2019 18:12:53 GMT</pubDate>
    <dc:creator>rwunderlich</dc:creator>
    <dc:date>2019-01-14T18:12:53Z</dc:date>
    <item>
      <title>Star-Scheme always best method?</title>
      <link>https://community.qlik.com/t5/QlikView/Star-Scheme-always-best-method/m-p/1529761#M438678</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am thinking about the statement, that a star scheme is always best Datamodel approach in QlikView.&lt;/P&gt;&lt;P&gt;In my concrete scenario I have a fact table, with a connected dimension table Company, where all Companies are listed. In a third table, all Company Countries are listed. Therefore this third table is connected to my second dimension Company.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would this not make more sense, when I am going with this snowflake scheme there would be for each Country&amp;nbsp; just one entry, and not for each Company one Country entry.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please advise.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Jan 2019 16:55:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Star-Scheme-always-best-method/m-p/1529761#M438678</guid>
      <dc:creator>chriys1337</dc:creator>
      <dc:date>2019-01-13T16:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: Star-Scheme always best method?</title>
      <link>https://community.qlik.com/t5/QlikView/Star-Scheme-always-best-method/m-p/1529769#M438680</link>
      <description>&lt;P&gt;I would not agree with the statement that a Star Schema is always best for Qlik.&amp;nbsp; It depends on how you want the model to behave and what problem you are trying to solve.&lt;/P&gt;&lt;P&gt;In a typical database system, storing the Country field in a separate table would be most efficient for storage as it would eliminate redundant entries.&amp;nbsp; Qlik stores data differently, so this redundancy issue is lessened or non-existent in some cases.&amp;nbsp;&lt;/P&gt;&lt;P&gt;A star schema &lt;EM&gt;generally&lt;/EM&gt; provides the best balance of&amp;nbsp; storage and CPU usage at runtime.&amp;nbsp; However, I would argue that in many cases, it's not worth spending time getting to a star.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My first rule is code for clarity and simplicity.&amp;nbsp; Make the model easy to understand and use, and minimize the time you spend on creating and maintaining the script.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Considering your example.&amp;nbsp; The separate&amp;nbsp; Customer and Company tables are likely the way the data exists in your source system.&amp;nbsp; Keeping it the same is easy to write the script and understand the model.&amp;nbsp; What if I want a count of countries that purchased each product?&amp;nbsp; Count(Country); easy.&amp;nbsp; If I join Company to Customer I have to change to Count(DISTINCT Country); more complex.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We &lt;EM&gt;may&lt;/EM&gt; be able to say that reducing the number of "hops" in a data model by going from snowflake to star would improve chart calc time by about 10%.&amp;nbsp; If a chart now takes 50 milliseconds to calc and we reduce it to 45, is that important?&amp;nbsp; Was it worth the effort?&amp;nbsp; If I have 50 daily users with 30 clicks each, it it probably not significant.&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Rob&lt;BR /&gt;&lt;A href="http://masterssummit.com" target="_blank"&gt;http://masterssummit.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://qlikviewcookbook.com" target="_blank"&gt;http://qlikviewcookbook.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.easyqlik.com" target="_blank"&gt;http://www.easyqlik.com&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2019 18:12:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Star-Scheme-always-best-method/m-p/1529769#M438680</guid>
      <dc:creator>rwunderlich</dc:creator>
      <dc:date>2019-01-14T18:12:53Z</dc:date>
    </item>
  </channel>
</rss>

