<?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: question on joins and keep in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/question-on-joins-and-keep/m-p/737019#M1054716</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;There are many reasons for using JOINs and KEEP depends on the user requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Suppose you have two tables and this are big table and associated with key field but if you create single table it load once and give performance also.&lt;/P&gt;&lt;P&gt;2. Second there is one &lt;/P&gt;&lt;P&gt;table1: &lt;EM&gt;EmpNo,Salary &lt;/EM&gt;and&lt;/P&gt;&lt;P&gt;table2: &lt;EM&gt;EmpNo, Commision, Address&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but user wants EmpNo,Salary,Salary+Commision.&lt;/P&gt;&lt;P&gt;On chart it is ok to perform but if he needs to do some more calculation like top and bottom once then if it is in single table will be better.&lt;/P&gt;&lt;P&gt;It depends how it is used&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 31 Oct 2014 12:20:39 GMT</pubDate>
    <dc:creator>its_anandrjs</dc:creator>
    <dc:date>2014-10-31T12:20:39Z</dc:date>
    <item>
      <title>question on joins and keep</title>
      <link>https://community.qlik.com/t5/QlikView/question-on-joins-and-keep/m-p/737017#M1054714</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;Hi Guys,&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; i know the diff b/n join and keep,but my question is in which situation we go for join,and in which situation we for keep?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;Regards,&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;koti&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 03:43:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/question-on-joins-and-keep/m-p/737017#M1054714</guid>
      <dc:creator>d_koti24</dc:creator>
      <dc:date>2014-10-31T03:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: question on joins and keep</title>
      <link>https://community.qlik.com/t5/QlikView/question-on-joins-and-keep/m-p/737018#M1054715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you need to do calculations or comparisons in the script using fields from different tables then you'll first have to join the tables. In other cases you are free to decide if you'd rather have separate tables and use the keep function or want to consolidate tables using joins. There can be a difference in performance. That's something you'll have to test yourself since it depends very much on your specific data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 12:12:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/question-on-joins-and-keep/m-p/737018#M1054715</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2014-10-31T12:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: question on joins and keep</title>
      <link>https://community.qlik.com/t5/QlikView/question-on-joins-and-keep/m-p/737019#M1054716</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;There are many reasons for using JOINs and KEEP depends on the user requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Suppose you have two tables and this are big table and associated with key field but if you create single table it load once and give performance also.&lt;/P&gt;&lt;P&gt;2. Second there is one &lt;/P&gt;&lt;P&gt;table1: &lt;EM&gt;EmpNo,Salary &lt;/EM&gt;and&lt;/P&gt;&lt;P&gt;table2: &lt;EM&gt;EmpNo, Commision, Address&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but user wants EmpNo,Salary,Salary+Commision.&lt;/P&gt;&lt;P&gt;On chart it is ok to perform but if he needs to do some more calculation like top and bottom once then if it is in single table will be better.&lt;/P&gt;&lt;P&gt;It depends how it is used&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 12:20:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/question-on-joins-and-keep/m-p/737019#M1054716</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-10-31T12:20:39Z</dc:date>
    </item>
  </channel>
</rss>

