Accepted Solutions
Yes, there's a message and it'll look like:
Roughly it's at a million records, but this can vary so do not depend on this. In general, I would highly recommend against exporting massive amounts of data from Qlik Sense. Qlik Sense is built to bring in data and visualize and wasn't designed to be as efficient as possible in getting data outside of it. As an overview, here's a sense of what all occurs when exporting data:
the Engine has to locate the associative [granular] data, construct a HyperCube in RAM on the box with the Engine, calculate visible aggregates, explode the HyperCube in memory and dump it to a temporary file, notify the browser that a temporary file is available, deliver it across the network, and then let the browser write the file to disk (taken from one of our very senior resources here)
Yes, there's a message and it'll look like:
Roughly it's at a million records, but this can vary so do not depend on this. In general, I would highly recommend against exporting massive amounts of data from Qlik Sense. Qlik Sense is built to bring in data and visualize and wasn't designed to be as efficient as possible in getting data outside of it. As an overview, here's a sense of what all occurs when exporting data:
the Engine has to locate the associative [granular] data, construct a HyperCube in RAM on the box with the Engine, calculate visible aggregates, explode the HyperCube in memory and dump it to a temporary file, notify the browser that a temporary file is available, deliver it across the network, and then let the browser write the file to disk (taken from one of our very senior resources here)
.png "Luminary Alumni"){kind=icon}
You can use the LogiExport extension to overcome the limitation.
the extension allows exporting a qlik sense objects to CSV files without rows limit, such as many other exciting features.
https://logiexport.logsys.co.il/documentation/
