<?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: AGGR using index fields - performance in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/AGGR-using-index-fields-performance/m-p/895414#M657758</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Often it worked to calculate measures over KEY's but they could be have unexpected results. Therefore if it's possible you should avoid it and from a performance point of view aggr-functions could take a lot of ressources especially if they grab the data from many tables. Further see here: &lt;A href="https://community.qlik.com/qlik-blogpost/2980"&gt;When should the Aggr() function NOT be used?&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Jun 2015 12:00:18 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2015-06-02T12:00:18Z</dc:date>
    <item>
      <title>AGGR using index fields - performance</title>
      <link>https://community.qlik.com/t5/QlikView/AGGR-using-index-fields-performance/m-p/895413#M657757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In an expression using AGGR, is it more performant to use a join field&lt;/P&gt;&lt;P&gt;=Sum(AGGR(ONLY([MyCount]), %%QV_RegnID))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or a non join field&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;=Sum(AGGR(ONLY([MyCount]), REGNID))&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;I know it's a bad idea to use join fields for display/ reporting but surely it's good to aggregate by an index? or is that not how QV works?&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jun 2015 11:47:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/AGGR-using-index-fields-performance/m-p/895413#M657757</guid>
      <dc:creator>georgina_spary</dc:creator>
      <dc:date>2015-06-02T11:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: AGGR using index fields - performance</title>
      <link>https://community.qlik.com/t5/QlikView/AGGR-using-index-fields-performance/m-p/895414#M657758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Often it worked to calculate measures over KEY's but they could be have unexpected results. Therefore if it's possible you should avoid it and from a performance point of view aggr-functions could take a lot of ressources especially if they grab the data from many tables. Further see here: &lt;A href="https://community.qlik.com/qlik-blogpost/2980"&gt;When should the Aggr() function NOT be used?&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jun 2015 12:00:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/AGGR-using-index-fields-performance/m-p/895414#M657758</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2015-06-02T12:00:18Z</dc:date>
    </item>
  </channel>
</rss>

