QlikView's columnar data storage method is extremely efficient at storing data because it does not store repeating values. Each unique value is only stored once. This means that, in general, a QlikView in-memory data set will always be much smaller than the original data source.
This efficiency is lost, however, when the data is highly distinct. The more distinct the values that exist within the data, the more space that QlikView will need to store it in memory. The worst offenders for this are often ID fields and time stamps, and if we can remove these, then we will make our document more efficient.
Load the following script:
// Build a list of city/countries City_Country: Load * Inline [ CityID, ...