<?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 Two fact tables - one big dimension table in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Two-fact-tables-one-big-dimension-table/m-p/192667#M54240</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have following scenario:&lt;/P&gt;&lt;P&gt;I have 2 quite big fact tables with three fields that I want to filter (each one separately).&lt;/P&gt;&lt;P&gt;My first idea is to create one dimension table. The problem is that when join 3 tables with 120 records each, as a result I would get table with 15625000 records. My application slows down immediately.&lt;/P&gt;&lt;P&gt;Maybe you have different way of handling this kind of situation?&lt;/P&gt;&lt;P&gt;Looking forward to hear from you all.&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Janusz&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Jun 2010 14:31:34 GMT</pubDate>
    <dc:creator />
    <dc:date>2010-06-17T14:31:34Z</dc:date>
    <item>
      <title>Two fact tables - one big dimension table</title>
      <link>https://community.qlik.com/t5/QlikView/Two-fact-tables-one-big-dimension-table/m-p/192667#M54240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have following scenario:&lt;/P&gt;&lt;P&gt;I have 2 quite big fact tables with three fields that I want to filter (each one separately).&lt;/P&gt;&lt;P&gt;My first idea is to create one dimension table. The problem is that when join 3 tables with 120 records each, as a result I would get table with 15625000 records. My application slows down immediately.&lt;/P&gt;&lt;P&gt;Maybe you have different way of handling this kind of situation?&lt;/P&gt;&lt;P&gt;Looking forward to hear from you all.&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Janusz&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 14:31:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Two-fact-tables-one-big-dimension-table/m-p/192667#M54240</guid>
      <dc:creator />
      <dc:date>2010-06-17T14:31:34Z</dc:date>
    </item>
    <item>
      <title>Two fact tables - one big dimension table</title>
      <link>https://community.qlik.com/t5/QlikView/Two-fact-tables-one-big-dimension-table/m-p/192668#M54241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I would build a link table that sits in the middle of all the tables,&lt;/P&gt;&lt;P&gt;There are various discussions on the community relatig to link tables, here is one of them:&lt;/P&gt;&lt;P&gt;&lt;A href="http://community.qlik.com/forums/t/16164.aspx"&gt;http://community.qlik.com/forums/t/16164.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Search for Link Table on the community to get more.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 14:55:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Two-fact-tables-one-big-dimension-table/m-p/192668#M54241</guid>
      <dc:creator />
      <dc:date>2010-06-17T14:55:58Z</dc:date>
    </item>
  </channel>
</rss>

