<?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: Link table instead of Joining in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935662#M323029</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on your data model. Link Table is generally used to avoid synthetic key/table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Oct 2015 09:37:56 GMT</pubDate>
    <dc:creator>MK_QSL</dc:creator>
    <dc:date>2015-10-08T09:37:56Z</dc:date>
    <item>
      <title>Link table instead of Joining</title>
      <link>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935661#M323028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use link table instead of joining fact tables, is there any performance issue because of this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2015 09:35:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935661#M323028</guid>
      <dc:creator />
      <dc:date>2015-10-08T09:35:57Z</dc:date>
    </item>
    <item>
      <title>Re: Link table instead of Joining</title>
      <link>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935662#M323029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on your data model. Link Table is generally used to avoid synthetic key/table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2015 09:37:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935662#M323029</guid>
      <dc:creator>MK_QSL</dc:creator>
      <dc:date>2015-10-08T09:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: Link table instead of Joining</title>
      <link>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935663#M323030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Joining fact tables is dangerous. You may duplicate records this way, and then numbers will be double counted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Concatenating fact tables is however safe - and usually has better performance than a link table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2015 09:46:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935663#M323030</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2015-10-08T09:46:00Z</dc:date>
    </item>
    <item>
      <title>Re: Link table instead of Joining</title>
      <link>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935664#M323031</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;&lt;/P&gt;&lt;P&gt;You can deal with multiple fact tables effectively with help of link table ....There will be some slow processing based on the data you have in fact tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But dont join fact tables in any case because you will lose control over your result set&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to solve this case only with concatination of fact tables&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Oct 2015 10:00:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Link-table-instead-of-Joining/m-p/935664#M323031</guid>
      <dc:creator />
      <dc:date>2015-10-08T10:00:40Z</dc:date>
    </item>
  </channel>
</rss>

