<?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 CONCATENATE vs JOIN in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190675#M53090</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Amien,&lt;/P&gt;&lt;P&gt;Both concatenate and join has different usabilty...&lt;/P&gt;&lt;P&gt;Concatenation :-&lt;/P&gt;&lt;P&gt;When u r Concatenating one table with another . Then the resultant table will have data of 1st table along with the added data of second table.&lt;/P&gt;&lt;P&gt;Like Suppose there is two table tab1 and tab2 having two fields a,b in common. If u do concatenate to these two tables then the resultant table has each &amp;amp; every data of first and second table with the same two filed name.&lt;/P&gt;&lt;P&gt;Join:-&lt;/P&gt;&lt;P&gt;There are different types of join.If u r going to compare join with concatenate then&lt;/P&gt;&lt;P&gt;Join between two tables result in the common values .&lt;/P&gt;&lt;P&gt;Like in the above scenario. Join of tab1 and tab2 results the common fieldvalueonce and not commonvalue is also once occured in the table.&lt;/P&gt;&lt;P&gt;Where as in concatenation the resultant field contains all the records although same value is repeated..&lt;/P&gt;&lt;P&gt;So looking in to this scenario join is better than concatenation when no of records and redundancy check come into picture.&lt;/P&gt;&lt;P&gt;Hope this will help you.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sunil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Dec 2010 07:29:35 GMT</pubDate>
    <dc:creator>sunil2288</dc:creator>
    <dc:date>2010-12-22T07:29:35Z</dc:date>
    <item>
      <title>CONCATENATE vs JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190672#M53087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What could be a reason to use concatenate? the result of a join looks much cleaner and memory efficient.&lt;/P&gt;&lt;P&gt;Do you prefer a join over een concatenate and why?&lt;/P&gt;&lt;P&gt;its clear that if database tables layout are the same that concatenate is preferered. so i'm more looking for reasons to use concatenate when tables are different and the result will look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;product | date | price | sold&lt;/P&gt;&lt;P&gt;shoes | 20100101 | 100 | -&lt;/P&gt;&lt;P&gt;shoes | 20100101 | - | 200&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;instead of&lt;/P&gt;&lt;P&gt;product | date | price | sold&lt;/P&gt;&lt;P&gt;shoes | 20100101 | 100 | 200&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Nov 2010 09:31:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190672#M53087</guid>
      <dc:creator>amien</dc:creator>
      <dc:date>2010-11-17T09:31:34Z</dc:date>
    </item>
    <item>
      <title>CONCATENATE vs JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190673#M53088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Amien,&lt;/P&gt;&lt;P&gt;In your example you talk about the same entity, in this case, products. But now think of getting a fact table built from different entities as invoices, shipment notes, delivery notes, stock and ledger entries, sales, purchases... each one with some common fields but some other required that are not shared. In this case, a join wouldn't make any sense, -there are no common fields or keys to join by-, and concatenation will work fine.&lt;/P&gt;&lt;P&gt;I haven't tested if concatenation performs better than join, since the ideal concatenation will require renaming of fields and create in each record the fields present in the other tables, but data is appended without taking care of already existing data (well, except for the fields to be created). A join requires at least one common field and reduction of data...&lt;/P&gt;&lt;P&gt;The result in both cases will be one table with all required data, which may be ok.&lt;/P&gt;&lt;P&gt;In your case, I would join rather than concatenate, but in many others, it will depend in the datamodel and the analyses required.&lt;/P&gt;&lt;P&gt;Hope this makes sense.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Nov 2010 09:50:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190673#M53088</guid>
      <dc:creator>Miguel_Angel_Baeyens</dc:creator>
      <dc:date>2010-11-17T09:50:01Z</dc:date>
    </item>
    <item>
      <title>CONCATENATE vs JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190674#M53089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;i think this link will help you&lt;/P&gt;&lt;P&gt;&lt;A href="http://qlikviewnotes.blogspot.com/2009/11/understanding-join-and-concatenate.html"&gt;http://qlikviewnotes.blogspot.com/2009/11/understanding-join-and-concatenate.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;it'll make you clear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Dec 2010 05:12:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190674#M53089</guid>
      <dc:creator>marcohadiyanto</dc:creator>
      <dc:date>2010-12-22T05:12:46Z</dc:date>
    </item>
    <item>
      <title>CONCATENATE vs JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190675#M53090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Amien,&lt;/P&gt;&lt;P&gt;Both concatenate and join has different usabilty...&lt;/P&gt;&lt;P&gt;Concatenation :-&lt;/P&gt;&lt;P&gt;When u r Concatenating one table with another . Then the resultant table will have data of 1st table along with the added data of second table.&lt;/P&gt;&lt;P&gt;Like Suppose there is two table tab1 and tab2 having two fields a,b in common. If u do concatenate to these two tables then the resultant table has each &amp;amp; every data of first and second table with the same two filed name.&lt;/P&gt;&lt;P&gt;Join:-&lt;/P&gt;&lt;P&gt;There are different types of join.If u r going to compare join with concatenate then&lt;/P&gt;&lt;P&gt;Join between two tables result in the common values .&lt;/P&gt;&lt;P&gt;Like in the above scenario. Join of tab1 and tab2 results the common fieldvalueonce and not commonvalue is also once occured in the table.&lt;/P&gt;&lt;P&gt;Where as in concatenation the resultant field contains all the records although same value is repeated..&lt;/P&gt;&lt;P&gt;So looking in to this scenario join is better than concatenation when no of records and redundancy check come into picture.&lt;/P&gt;&lt;P&gt;Hope this will help you.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sunil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Dec 2010 07:29:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190675#M53090</guid>
      <dc:creator>sunil2288</dc:creator>
      <dc:date>2010-12-22T07:29:35Z</dc:date>
    </item>
    <item>
      <title>CONCATENATE vs JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190676#M53091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here join is better preferred.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Dec 2010 07:31:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/CONCATENATE-vs-JOIN/m-p/190676#M53091</guid>
      <dc:creator>sunil2288</dc:creator>
      <dc:date>2010-12-22T07:31:04Z</dc:date>
    </item>
  </channel>
</rss>

