<?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: keep n join in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767567#M272630</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, that conclusion doesn't automatically follow from that. Perhaps this blog post helps: &lt;A _jive_internal="true" class="font-color-normal" href="https://community.qlik.com/blogs/qlikviewdesignblog/2015/01/19/number-of-hops" style="font-weight: inherit; font-style: inherit; font-family: inherit; color: #3d3d3d;"&gt;A Myth about the Number of Hops&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Feb 2015 10:06:08 GMT</pubDate>
    <dc:creator>Gysbert_Wassenaar</dc:creator>
    <dc:date>2015-02-09T10:06:08Z</dc:date>
    <item>
      <title>keep n join</title>
      <link>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767564#M272627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;when we use keep between two tables, the two tables will be kept as separate tables.&lt;/P&gt;&lt;P&gt;where as in join; they will be clubbed.&lt;/P&gt;&lt;P&gt;so, can we say that extra memory will be occupied in 1 st case and tat would degrade performance?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2015 10:01:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767564#M272627</guid>
      <dc:creator />
      <dc:date>2015-02-09T10:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: keep n join</title>
      <link>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767565#M272628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Grom Help: take a look to the NOTE:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The &lt;SPAN class="Bold"&gt;keep&lt;/SPAN&gt; prefix is similar to the &lt;A class="MCXref_0" href="https://community.qlik.com/"&gt;&lt;EM style=": ; color: #0066cc; text-decoration: underline;"&gt;Join&lt;/EM&gt;&lt;/A&gt; prefix. Just as the join prefix, it compares the loaded table with an existing named table or the last previously created data table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But instead of joining the loaded table with an existing table, it has the effect of reducing one or both of the two tables before they are stored in QlikView, based on the intersection of table data. The comparison made is equivalent to a natural join made over all the common fields, i.e. the same way as in a corresponding join. However, the two tables are not joined and will be kept in QlikView as two separately named tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV class="note"&gt;&lt;SPAN class="Bold"&gt;Note!&lt;/SPAN&gt; &lt;BR /&gt;The explicit &lt;A class="MCXref_0" href="https://community.qlik.com/"&gt;&lt;EM style=": ; color: #0066cc; text-decoration: underline;"&gt;Join&lt;/EM&gt;&lt;/A&gt; prefix in QlikView script language performs a full join of the two tables. The result is one table. In many cases such joins will result in very large tables. One of the main features of QlikView is its ability to make associations between multiple tables instead of joining them, which greatly reduces memory usage, increases processing speed and offers enormous flexibility. Explicit joins should therefore generally be avoided in QlikView scripts. The &lt;SPAN class="Bold"&gt;keep&lt;/SPAN&gt; functionality was designed to reduce the number of cases where explicit joins needs to be used.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2015 10:05:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767565#M272628</guid>
      <dc:creator>alexandros17</dc:creator>
      <dc:date>2015-02-09T10:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: keep n join</title>
      <link>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767566#M272629</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Prudhvi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually we use keep whenever u need to track data as it will create two separate tables while in case of join it will store data in a single table so it would be difficult to track down the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kushal T&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2015 10:05:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767566#M272629</guid>
      <dc:creator>kushalthakral</dc:creator>
      <dc:date>2015-02-09T10:05:22Z</dc:date>
    </item>
    <item>
      <title>Re: keep n join</title>
      <link>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767567#M272630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, that conclusion doesn't automatically follow from that. Perhaps this blog post helps: &lt;A _jive_internal="true" class="font-color-normal" href="https://community.qlik.com/blogs/qlikviewdesignblog/2015/01/19/number-of-hops" style="font-weight: inherit; font-style: inherit; font-family: inherit; color: #3d3d3d;"&gt;A Myth about the Number of Hops&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2015 10:06:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767567#M272630</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2015-02-09T10:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: keep n join</title>
      <link>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767568#M272631</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;I like &lt;A href="https://community.qlik.com/qlik-users/2226"&gt;JohnW&lt;/A&gt; opinion here: &lt;/SPAN&gt;&lt;A _jive_internal="true" data-containerid="2051" data-containertype="14" data-objectid="13858" data-objecttype="2" href="https://community.qlik.com/message/13858#13858"&gt;http://community.qlik.com/message/13858#13858&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; in this regard.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2015 10:10:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/keep-n-join/m-p/767568#M272631</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2015-02-09T10:10:37Z</dc:date>
    </item>
  </channel>
</rss>

