<?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 Doubt in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Doubt/m-p/521145#M194723</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;&lt;/P&gt;&lt;P&gt;i have one doubt in using join and keep&lt;/P&gt;&lt;P&gt;when i have two tables &lt;STRONG&gt;join&lt;/STRONG&gt; will make it one table,&lt;/P&gt;&lt;P&gt;when i have two tables &lt;STRONG&gt;keep&lt;/STRONG&gt; will make it as it is,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in data model keep will give bad performance ,Then why we are preferring Keep&amp;nbsp; instated on join,and usage of keep&lt;/P&gt;&lt;P&gt;Please some one explain me &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks In Advance&lt;/P&gt;&lt;P&gt;Niranjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Dec 2013 08:59:06 GMT</pubDate>
    <dc:creator>NavinReddy</dc:creator>
    <dc:date>2013-12-24T08:59:06Z</dc:date>
    <item>
      <title>Doubt</title>
      <link>https://community.qlik.com/t5/QlikView/Doubt/m-p/521145#M194723</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;&lt;/P&gt;&lt;P&gt;i have one doubt in using join and keep&lt;/P&gt;&lt;P&gt;when i have two tables &lt;STRONG&gt;join&lt;/STRONG&gt; will make it one table,&lt;/P&gt;&lt;P&gt;when i have two tables &lt;STRONG&gt;keep&lt;/STRONG&gt; will make it as it is,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in data model keep will give bad performance ,Then why we are preferring Keep&amp;nbsp; instated on join,and usage of keep&lt;/P&gt;&lt;P&gt;Please some one explain me &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks In Advance&lt;/P&gt;&lt;P&gt;Niranjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Dec 2013 08:59:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Doubt/m-p/521145#M194723</guid>
      <dc:creator>NavinReddy</dc:creator>
      <dc:date>2013-12-24T08:59:06Z</dc:date>
    </item>
    <item>
      <title>Re: Doubt</title>
      <link>https://community.qlik.com/t5/QlikView/Doubt/m-p/521146#M194724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See here : &lt;A href="https://community.qlik.com/docs/DOC-3412"&gt;Joins and Lookups&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Dec 2013 09:03:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Doubt/m-p/521146#M194724</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2013-12-24T09:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: Doubt</title>
      <link>https://community.qlik.com/t5/QlikView/Doubt/m-p/521147#M194725</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;un appropiate use of joins may leed to duplication of rows in case of joins&lt;/P&gt;&lt;P&gt;and that often happens but keep the left or right tables as also&amp;nbsp; maintaing the join condition and&lt;/P&gt;&lt;P&gt;filtering of rows accordind to inner,outer,left , right join in most scenarios keep do not duplicate data&lt;/P&gt;&lt;P&gt;or corrupt data but this happens but nothing like join is worst and keep is best it is just that there in appropiate&lt;/P&gt;&lt;P&gt;use leeds to error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;anant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Dec 2013 09:06:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Doubt/m-p/521147#M194725</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-24T09:06:32Z</dc:date>
    </item>
    <item>
      <title>Re: Doubt</title>
      <link>https://community.qlik.com/t5/QlikView/Doubt/m-p/521148#M194726</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your replay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Niranjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Dec 2013 09:13:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Doubt/m-p/521148#M194726</guid>
      <dc:creator>NavinReddy</dc:creator>
      <dc:date>2013-12-24T09:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: Doubt</title>
      <link>https://community.qlik.com/t5/QlikView/Doubt/m-p/521149#M194727</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"Keep" will &lt;EM&gt;&lt;SPAN style="text-decoration: underline;"&gt;not&lt;/SPAN&gt; &lt;/EM&gt;per se give bad performance. It is the most efficient way to remove unwanted records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And your data model &lt;EM style="text-decoration: underline;"&gt;should&lt;/EM&gt; in most cases contain several tables. See more on &lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2012/09/12/to-join-or-not-to-join"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2012/09/12/to-join-or-not-to-join&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jan 2014 16:41:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Doubt/m-p/521149#M194727</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2014-01-17T16:41:14Z</dc:date>
    </item>
  </channel>
</rss>

