topic Re: Performance Issues - Pitch in QlikView

Performance Issues - Pitch

Mon, 26 Jan 2026 18:19:17 GMT

Hello everyone,

we are trying to compete against another Software with our Qlik knowledge and asking ourselves how Qlik works internally.

What happens if I am using a set analysis like sum({<Week={'1'}>} Value)? Is it like a part aggregation of the flat table or more a calculation on the whole table?

Which indexes are build on the data table if there are any?

Our data table has a few values, dimensions and especially dates.

Thank you in advance,

tuffelchen

Re: Performance Issues - Pitch

annafuksa1 — Mon, 16 Jan 2017 13:28:12 GMT

in this case you will have sum of values only for week 1 (even if select any other week) and for current selection (click clear to clean it if you do not wish it)

Anna

Re: Performance Issues - Pitch

Mon, 16 Jan 2017 13:29:58 GMT

It's the question about the result but what is calculated and especially how it is calculated.

Re: Performance Issues - Pitch

annafuksa1 — Mon, 16 Jan 2017 13:48:24 GMT

the aggregation happens in the table on your dimension level.

Indexes are being build when reloading the script.

Re: Performance Issues - Pitch

Mon, 16 Jan 2017 13:52:26 GMT

so the sql statement 'select sum(Value) from table group by Week where Week=1' or 'select sum(Value) from table where Week=1' is calculated?

Re: Performance Issues - Pitch

annafuksa1 — Mon, 16 Jan 2017 14:09:39 GMT

if you will add Week as dimension then option 1 if no dimension option 2

Re: Performance Issues - Pitch

annafuksa1 — Mon, 16 Jan 2017 14:10:46 GMT

option 1 will be exactly

'select Week, sum(Value) from table group by Week where Week=1'

Re: Performance Issues - Pitch

marcus_sommer — Mon, 16 Jan 2017 14:28:55 GMT

The set analysis is not part of the aggregation - it's more a kind of two-step calculation in which the set analysis will be applied like a sql where-clause against the dataset - returning true or false - and only on the remaining records will be the aggregation calculated.

But it will be depend on various factors if this type of expression is the fasted one within your datamodel. Changes within the datamodel regarding to a star-scheme, snowflake-scheme or a big flat-table could make a big difference to the response-time form the UI - for example it could be useful to create flags for your most used and most heavier aggregations, like: sum(Value * Week1Flag). In each case you need to avoid string-comparings like '1' and use instead pure numeric values.

- Marcus