<?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: ApplyMap load speed vs lookup table in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879974#M307093</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That all depends on the size of your data. The difference between using a translated field in the same table as the original text vs a separate normalised table through a link is minimal, according to the Qlik gods. See &lt;A href="https://community.qlik.com/qlik-blogpost/4039"&gt;A Myth about the Number of Hops&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 May 2015 12:37:14 GMT</pubDate>
    <dc:creator>Peter_Cammaert</dc:creator>
    <dc:date>2015-05-18T12:37:14Z</dc:date>
    <item>
      <title>ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879971#M307090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good day all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a large data set that contains many acronyms and abbreviations. I would like to convert these into their long text translations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is: is it faster to ApplyMap these values directly into the FACT table or keep the values in their own lookup table?&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture.PNG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/86807_Capture.PNG" style="height: auto;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 12:20:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879971#M307090</guid>
      <dc:creator />
      <dc:date>2015-05-18T12:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879972#M307091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ApplyMap is much faster than LookUp Function. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go thru this link for detailed information&lt;/P&gt;&lt;P&gt;&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>Mon, 18 May 2015 12:26:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879972#M307091</guid>
      <dc:creator>manojkulkarni</dc:creator>
      <dc:date>2015-05-18T12:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879973#M307092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Keeping them in their own lookup table would obviously be faster, because that doesn't require any comparison, it is just a simple table load. The comparison could have been a valid one had you thought of joining it or just mapping it, where the apply map would have been faster.&lt;/P&gt;&lt;P&gt;If you keep them in separate tables, the load would be faster, however, the front-end performance would be a bit slower than it could be they were joined or apply mapped to form a single table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 12:34:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879973#M307092</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2015-05-18T12:34:14Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879974#M307093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That all depends on the size of your data. The difference between using a translated field in the same table as the original text vs a separate normalised table through a link is minimal, according to the Qlik gods. See &lt;A href="https://community.qlik.com/qlik-blogpost/4039"&gt;A Myth about the Number of Hops&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 12:37:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879974#M307093</guid>
      <dc:creator>Peter_Cammaert</dc:creator>
      <dc:date>2015-05-18T12:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879975#M307094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ApplyMap is faster, use Lookup if you need to add more than 1 field to your fact table, although you would better off having a number of Mapping Tables and using ApplyMap&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 12:46:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879975#M307094</guid>
      <dc:creator>rustyfishbones</dc:creator>
      <dc:date>2015-05-18T12:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879976#M307095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply. So, leaving the long text as an associated value in a seperate table would be quicker in the front end than using mapping tables?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 12:56:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879976#M307095</guid>
      <dc:creator />
      <dc:date>2015-05-18T12:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879977#M307096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, I should clarify; I wanted a comparison with a lookup table, not the LookUp() function. Thanks for your reply.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 12:56:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879977#M307096</guid>
      <dc:creator />
      <dc:date>2015-05-18T12:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap load speed vs lookup table</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879978#M307097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, it's otherwise. Faster in the back-end. And slower in the front-end, but that could be negligible based on your data size.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 13:03:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap-load-speed-vs-lookup-table/m-p/879978#M307097</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2015-05-18T13:03:55Z</dc:date>
    </item>
  </channel>
</rss>

