<?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 joins in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/joins/m-p/1357612#M823076</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i have two tables for each table have 10 fields but i want to join 1 field in both table and suggest which function takes less memory and with fast operation&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
    <dc:creator>manoj217</dc:creator>
    <dc:date>2020-11-25T16:16:04Z</dc:date>
    <item>
      <title>joins</title>
      <link>https://community.qlik.com/t5/QlikView/joins/m-p/1357612#M823076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i have two tables for each table have 10 fields but i want to join 1 field in both table and suggest which function takes less memory and with fast operation&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/joins/m-p/1357612#M823076</guid>
      <dc:creator>manoj217</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: joins</title>
      <link>https://community.qlik.com/t5/QlikView/joins/m-p/1357613#M823077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi manoj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just have the fields you want to join have the same name while all the rest of the fields in both tables should have unique names.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Uri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2017 06:22:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/joins/m-p/1357613#M823077</guid>
      <dc:creator>sonkumamon</dc:creator>
      <dc:date>2017-07-24T06:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: joins</title>
      <link>https://community.qlik.com/t5/QlikView/joins/m-p/1357614#M823078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If there are different numbers of rows in each table (i.e. it is not a perfect unique key on both sides) then your best bet is certainly just to load them both in and have them associate in the data model on the single field that joins.&amp;nbsp; Just make sure the field is named exactly the same on both sides.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there are identical numbers of rows and perfect keys in the tables then a JOIN would be a better approach (ideally in SQL, but in Qlik script is fine also).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there are only two or three columns in one of the tables then ApplyMap would be best.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are not totally hard and fast rules - but certainly a good start point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2017 06:44:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/joins/m-p/1357614#M823078</guid>
      <dc:creator>stevedark</dc:creator>
      <dc:date>2017-07-24T06:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: joins</title>
      <link>https://community.qlik.com/t5/QlikView/joins/m-p/1357615#M823079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Manoj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I Agree with Steve . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Arvind Patil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2017 07:00:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/joins/m-p/1357615#M823079</guid>
      <dc:creator>arvind_patil</dc:creator>
      <dc:date>2017-07-24T07:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: joins</title>
      <link>https://community.qlik.com/t5/QlikView/joins/m-p/1357616#M823080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Manoj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no such rule for when to use join/concatenate or any other concept, it will change project to project according to requirement and data model.&lt;/P&gt;&lt;P&gt;You just have to be make sure about your data model/qvd's need to be optimized which will increase data model performance .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Neha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2017 11:31:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/joins/m-p/1357616#M823080</guid>
      <dc:creator>neha_shirsath</dc:creator>
      <dc:date>2017-07-24T11:31:58Z</dc:date>
    </item>
    <item>
      <title>Re: joins</title>
      <link>https://community.qlik.com/t5/QlikView/joins/m-p/1357617#M823081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Manoj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no such type of concepts, according to your requirement we have to follow &lt;STRONG&gt;Join/Concatenate/Keep&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;EM&gt;&lt;STRONG&gt;Join &lt;/STRONG&gt;&lt;/EM&gt;can be used to tackle the same kind of situation, but there is a difference which should be understood.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;EM&gt;Join&lt;/EM&gt; will combine the rows where the key values matches.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;EM&gt;&lt;STRONG&gt;Concatenate&lt;/STRONG&gt;&lt;/EM&gt;&lt;STRONG&gt; &lt;/STRONG&gt;append the rows of one table to another table. Conacetnate never merges any rows in it. &lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;EM&gt;&lt;STRONG&gt;Keep&lt;/STRONG&gt;&lt;/EM&gt; two tables are not joined and will be stored in 2 separately named tables.&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt;The keep keyword must always be preceded by one of the prefixes Inner, Left or Right&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2017 12:25:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/joins/m-p/1357617#M823081</guid>
      <dc:creator>Nagaraju_KCS</dc:creator>
      <dc:date>2017-07-24T12:25:57Z</dc:date>
    </item>
  </channel>
</rss>

