Creating counter fields to avoid Count Distinct

Using a Count function is a very common use case in any type of reporting. However, it is also a very laborious calculation, requiring many more CPU cycles than, say, a Sum function. This is because a function like Sum is actually a very low-level function, operating almost at the CPU level, whereas a function like Count is more high-level, operating at the application code level. On a multi-threaded system (which means almost all systems nowadays), the Sum function will run across all cores whereas the Count function will only calculate on one thread.

If we can avoid Count functions, especially a Count function with a Distinct clause, then we will have a more efficient application.

Getting ready ...

Get QlikView for Developers Cookbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.