<?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 keyword in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253951#M857891</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This has been discussed here: &lt;A href="https://community.qlik.com/message/714759"&gt;Re: KEEP command - why to use that?&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Jan 2017 08:56:58 GMT</pubDate>
    <dc:creator>tresB</dc:creator>
    <dc:date>2017-01-30T08:56:58Z</dc:date>
    <item>
      <title>Keep keyword</title>
      <link>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253949#M857889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;Would anyone can tell me the purpose/use of keep keyword. I read it you can use it JOIN/KEEP keyword where join will join and will show 1 table, KEEP keyword keeps 2 tables. my question is that why we would need KEEP keyword in real time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253949#M857889</guid>
      <dc:creator />
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Keep keyword</title>
      <link>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253950#M857890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Eg &lt;/P&gt;&lt;P&gt;If you have table 1 with 10 columns and 10K records and&amp;nbsp; table 2 with 4 columns and 20 records.&lt;/P&gt;&lt;P&gt;In this case if you join the table2 with table1 then it will generate 10K records for the 3 columns in the table1 which is not feasible intend of that&amp;nbsp;&amp;nbsp; &lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 10pt;"&gt;Keep just reduce the data in the table 2 in accordance with table 1 without joining and creating additional &lt;/SPAN&gt;records&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-size: 10pt;"&gt;Hope this helps you&amp;nbsp; &lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jan 2017 08:55:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253950#M857890</guid>
      <dc:creator>avinashelite</dc:creator>
      <dc:date>2017-01-30T08:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: Keep keyword</title>
      <link>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253951#M857891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This has been discussed here: &lt;A href="https://community.qlik.com/message/714759"&gt;Re: KEEP command - why to use that?&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jan 2017 08:56:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253951#M857891</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2017-01-30T08:56:58Z</dc:date>
    </item>
    <item>
      <title>Re: Keep keyword</title>
      <link>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253952#M857892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;read this thread&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/thread/39177"&gt;Understanding Join, Keep and Concatenate&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jan 2017 09:40:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253952#M857892</guid>
      <dc:creator>vinieme12</dc:creator>
      <dc:date>2017-01-30T09:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: Keep keyword</title>
      <link>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253953#M857893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are many advantages of keep compared to join but it depends on the scenario:&lt;/P&gt;&lt;P&gt;It will avoid one to many relation wrong calculations,check here &lt;A href="https://community.qlik.com/thread/165357"&gt;when to use Join and when to use Keep ?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;its use can also reduce the table size.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take scenario where u have master calendar with future date and there is one main data table.Its not recommended to join data with calendar, though you can associate but using Keep will also solve the purpose and also reduce the data size by comparing dates in main table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jan 2017 09:44:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253953#M857893</guid>
      <dc:creator>sdmech81</dc:creator>
      <dc:date>2017-01-30T09:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: Keep keyword</title>
      <link>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253954#M857894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One scenario that I commonly use is to reduce dimensions so that only the relevant dimension values get loaded 0 like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Transactions:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;LOAD TransID,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp; TypeCode,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp; ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Left Keep(Transactions)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;TypeCodes:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;LOAD TypeCode,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp; TypeDescription,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp; TypeCategory,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp; ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But one could also use this for the same result:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;Transactions:&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;LOAD TransID,&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;&amp;nbsp; TypeCode,&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;&amp;nbsp; ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;TypeCodes:&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;LOAD TypeCode,&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;&amp;nbsp; TypeDescription,&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;&amp;nbsp; TypeCategory,&lt;/EM&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;EM&gt;&amp;nbsp; ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;WHERE Exists(TypeCode)&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jan 2017 09:55:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Keep-keyword/m-p/1253954#M857894</guid>
      <dc:creator>jonathandienst</dc:creator>
      <dc:date>2017-01-30T09:55:06Z</dc:date>
    </item>
  </channel>
</rss>

