<?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: Which scenarios link table is good? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711300#M1077577</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's really thank you Sir.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 19 Jul 2014 15:28:06 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-07-19T15:28:06Z</dc:date>
    <item>
      <title>Which scenarios link table is good?</title>
      <link>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711296#M1077573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Explain With practical examples any body sir. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jul 2014 14:15:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711296#M1077573</guid>
      <dc:creator />
      <dc:date>2014-07-19T14:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: Which scenarios link table is good?</title>
      <link>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711297#M1077574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ramesh,&lt;/P&gt;&lt;P&gt;It’s hard to find a general rule to determine when you should Concatenate rather than joining tables by a Link Table .&lt;/P&gt;&lt;P&gt;You probably check out the following blog and read the attached document. &lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2013/05/17/concatenate-vs-link-table"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2013/05/17/concatenate-vs-link-table&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jul 2014 14:25:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711297#M1077574</guid>
      <dc:creator>Siva_Sankar</dc:creator>
      <dc:date>2014-07-19T14:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: Which scenarios link table is good?</title>
      <link>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711298#M1077575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I quote from &lt;A href="https://community.qlik.com/qlik-users/2310"&gt;Oleg Troyansky&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;EM style="color: #993300;"&gt;Concatenated Facts perform much better than data structures with Link Tables &lt;/EM&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; www.naturalsynergies.com/q-tip-9-concatenate-or-join/ &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jul 2014 14:29:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711298#M1077575</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-07-19T14:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: Which scenarios link table is good?</title>
      <link>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711299#M1077576</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bill&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Textual of the book Qlikview for developers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Finding a Balance"&lt;/P&gt;&lt;P&gt;We have outlined two ways for dealing with multiple fact tables in data model, if we were to ask which of these method is better(concatenate or link table), we would need to say "IT DEPENDS".&lt;/P&gt;&lt;P&gt;There is no define best, and the decision about which to use will depend entirely on the specific scenario where it has to be implemented."&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jul 2014 14:51:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711299#M1077576</guid>
      <dc:creator>fkeuroglian</dc:creator>
      <dc:date>2014-07-19T14:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: Which scenarios link table is good?</title>
      <link>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711300#M1077577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's really thank you Sir.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jul 2014 15:28:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711300#M1077577</guid>
      <dc:creator />
      <dc:date>2014-07-19T15:28:06Z</dc:date>
    </item>
    <item>
      <title>Re: Which scenarios link table is good?</title>
      <link>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711301#M1077578</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Because Qlikview is excellent at compressing duplicate values, concatenate is generally my first instinct.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Link Tables, in my opinion, should only be used when concatenate simply does not make sense.&amp;nbsp; For example, creating a Canonical Calendar .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Jan 2015 22:31:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Which-scenarios-link-table-is-good/m-p/711301#M1077578</guid>
      <dc:creator />
      <dc:date>2015-01-04T22:31:09Z</dc:date>
    </item>
  </channel>
</rss>

