<?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: Data layer design in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346345#M128145</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;Duplication of dimension tables will not affect performance - only file size and memory usage.&lt;/P&gt;&lt;P&gt;Link tables is one way of handling two or more fact tables, but if you can, try and combine (concatenate) fact tables into ONE fact table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use a field ROWTYPE for the different types of fact rows.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/21613"&gt;Magnus Åvitsland&lt;/A&gt;&lt;/P&gt;&lt;P&gt;BI Consultant&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.framsteg.com" target="_blank"&gt;Framsteg Business Intelligence Corp.&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Apr 2012 14:00:10 GMT</pubDate>
    <dc:creator>magavi_framsteg</dc:creator>
    <dc:date>2012-04-11T14:00:10Z</dc:date>
    <item>
      <title>Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346341#M128141</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;I have a data model with 2 fact tables and 10 dimnsion tables. Primary fact table is connected to all 10 dimension tables through foreign keys and secondary fact table is connected to 6 dimesion tables (out of 10) through foreign keys only. When I make such joins in Qlikview , it is making a synthetic key and table of common 6 foreign keys, resulting into very bad performance of the file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please guide regarding best approach of design of this data layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Apr 2012 09:31:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346341#M128141</guid>
      <dc:creator />
      <dc:date>2012-04-11T09:31:24Z</dc:date>
    </item>
    <item>
      <title>Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346342#M128142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can duplicate the dimension tables. So DimensionA1 will join to one fact table and DimensionA2 (which is the same dimension) join it to the other fact table&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Apr 2012 09:35:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346342#M128142</guid>
      <dc:creator>jvitantonio</dc:creator>
      <dc:date>2012-04-11T09:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346343#M128143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Or you can, if possible, combine (concatenate) the two fact tables into one fact table and join all 10 dimension tables to the one fact table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/21613"&gt;Magnus Åvitsland&lt;/A&gt;&lt;/P&gt;&lt;P&gt;BI Consultant&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.framsteg.com" target="_blank"&gt;Framsteg Business Intelligence Corp.&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Apr 2012 13:44:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346343#M128143</guid>
      <dc:creator>magavi_framsteg</dc:creator>
      <dc:date>2012-04-11T13:44:13Z</dc:date>
    </item>
    <item>
      <title>Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346344#M128144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Will duplicating dimesion tables not affect perforamnce of report?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have tried concatenation but that is not giving results in further calculation on fields from both fact tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does any body has any idea about link table?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Apr 2012 13:50:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346344#M128144</guid>
      <dc:creator />
      <dc:date>2012-04-11T13:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346345#M128145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;Duplication of dimension tables will not affect performance - only file size and memory usage.&lt;/P&gt;&lt;P&gt;Link tables is one way of handling two or more fact tables, but if you can, try and combine (concatenate) fact tables into ONE fact table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use a field ROWTYPE for the different types of fact rows.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/21613"&gt;Magnus Åvitsland&lt;/A&gt;&lt;/P&gt;&lt;P&gt;BI Consultant&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.framsteg.com" target="_blank"&gt;Framsteg Business Intelligence Corp.&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Apr 2012 14:00:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346345#M128145</guid>
      <dc:creator>magavi_framsteg</dc:creator>
      <dc:date>2012-04-11T14:00:10Z</dc:date>
    </item>
    <item>
      <title>Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346346#M128146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to calculate division of one field of primary fact table with another field of secondary fact table at UI level in pivot table. Will concatenation of these 2 fact tables give me correct results?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Apr 2012 14:49:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346346#M128146</guid>
      <dc:creator />
      <dc:date>2012-04-11T14:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346347#M128147</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I reckon it will give the same correct result.&lt;/P&gt;&lt;P&gt;You could always do a quick test with inline tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Test 1 with two fact tables.&lt;/P&gt;&lt;P&gt;Test 2 one fact table consisting of the two concatenated fact tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/21613"&gt;Magnus Åvitsland&lt;/A&gt;&lt;/P&gt;&lt;P&gt;BI Consultant&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.framsteg.com" target="_blank"&gt;Framsteg Business Intelligence Corp.&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Apr 2012 08:13:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346347#M128147</guid>
      <dc:creator>magavi_framsteg</dc:creator>
      <dc:date>2012-04-12T08:13:15Z</dc:date>
    </item>
    <item>
      <title>Data layer design</title>
      <link>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346348#M128148</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Magnus mentioned, I'd try to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1-concatenate both fact tables into one. As a general rule (sometimes it may not be true), the star schema will have better overall preformance&lt;/P&gt;&lt;P&gt;2-create a link table to join the dimensions to the 2 fact tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not really an expert (yet... &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;) but the duplicated dimension solution seems kinda strange to me...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 03:29:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-layer-design/m-p/346348#M128148</guid>
      <dc:creator>fosuzuki</dc:creator>
      <dc:date>2012-04-13T03:29:46Z</dc:date>
    </item>
  </channel>
</rss>

