I'm aware that one of the reasons why Qlik apps may grow very quickly is due to cardinality (having many non unique records).
I wonder if you have good techniques to deal with timestamps. In the app I'm working at I have roughly 800,000 records with a unique ID, a text description (this I can't avoid being unique either) but also two columns with timestamps that maybe I could be storing in a better way. What do you think?
Is there a functional need for time? if not remove the time from date using floor function. if time is needed split the timestamp into date and time fields
You can also look at reducing the precision of the timestamps (e.g. remove milliseconds or seconds) in addition to or instead of splitting into date/time.
