<?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: In which scenario snow flake is good in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588755#M1099030</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Suppose you have data for date not in single table but in different table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Date(Table) &amp;gt;&amp;gt; Month(Table) &amp;gt;&amp;gt; Quarter(Table) &amp;gt;&amp;gt; Year(Table)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so in above if you want to refer to year you need to refer to all sub tables and then you get info about the year like same way other for month also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so if all in single table like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CalendarTable:&lt;/P&gt;&lt;P&gt;Date,Month,Quarter,Year&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will be easy and performance wise is good but if data is huge you feel the performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Apr 2014 05:53:12 GMT</pubDate>
    <dc:creator>its_anandrjs</dc:creator>
    <dc:date>2014-04-17T05:53:12Z</dc:date>
    <item>
      <title>In which scenario snow flake is good</title>
      <link>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588752#M1099027</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi can any body tell me in which scenario should we go for snow flake schema&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2014 04:34:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588752#M1099027</guid>
      <dc:creator />
      <dc:date>2014-04-17T04:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: In which scenario snow flake is good</title>
      <link>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588753#M1099028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is good when you have dimension and sub dimension then it is use like snow flake schema but normally we try to use star flake schema because in snow flake schema we have to refer to its child tables.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2014 04:42:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588753#M1099028</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-04-17T04:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: In which scenario snow flake is good</title>
      <link>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588754#M1099029</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;If your database is normalized then snowflake is used, but there are performance issues using this schema, because at the number of joins are increased.&amp;nbsp; That is why in Qlikview Star Schema is preferred, snowflake is converted to star by joining the Fact and Sub Fact tables.&amp;nbsp; For less data you can't the performance issues, but when the data is huge you can notice the performace issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;SnowFlake : Region (Table) -&amp;gt; Country(Table) -&amp;gt; City (Table) (All are separate fact tables)&lt;/P&gt;&lt;P&gt;Star : One table has all the fields (by joining all the tables)&lt;/P&gt;&lt;P&gt;Hope this helps you.&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;Jagan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2014 05:40:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588754#M1099029</guid>
      <dc:creator>jagan</dc:creator>
      <dc:date>2014-04-17T05:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: In which scenario snow flake is good</title>
      <link>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588755#M1099030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Suppose you have data for date not in single table but in different table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Date(Table) &amp;gt;&amp;gt; Month(Table) &amp;gt;&amp;gt; Quarter(Table) &amp;gt;&amp;gt; Year(Table)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so in above if you want to refer to year you need to refer to all sub tables and then you get info about the year like same way other for month also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so if all in single table like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CalendarTable:&lt;/P&gt;&lt;P&gt;Date,Month,Quarter,Year&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will be easy and performance wise is good but if data is huge you feel the performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2014 05:53:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/In-which-scenario-snow-flake-is-good/m-p/588755#M1099030</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-04-17T05:53:12Z</dc:date>
    </item>
  </channel>
</rss>

