Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
trengsoba
Contributor
Contributor

Memory Errror in Qlik Cloud - How can I trim my data more?

I am ending up loading thousands and thousands of pieces of information on imports.

If my foremost consumer is 123, and that i handiest want to load facts for client 123, i'm the usage of:

Where "CMNUM" in ('123');
This does brilliant, it pulls most effective the shipments associated with this customer identity.

From here I need to tug the information in this shipment; together with quantity, item description, object weight, item value.

Shipment xyz is my demo cargo. I

But this is in which i am getting into hassle. As I pass to loud the next sets of records, How do I say best load gadgets which can be observed in shipment xyz. And do the equal for all the different fields. Be aware at the same time as xyz is my test, I want to load all statistics relating to purchaser 123, but no other data.

Presently once I load my statistics its looking like this, and that is handiest about 30% of the burden system.

Traces fetched: 138,444
Lines fetched: 417,422 strains fetched: three hundred,148 lines fetched: 763,173 strains fetched: 525,950 strains fetched: 417,977 lines fetched: 448,193

Complete script takes approximately three minutes to load, except after I add element description, rate, which are in the identical desk, and have 1.5m consequences. It then runs the server out of memory, and fails to loud, often inflicting different human beings on our server troubles as well, forcing a restart of the server.

I presently do no longer have the luxurious of the usage of QVD documents, however operating on getting it setup.

Labels (2)
1 Reply
marcus_sommer

The size of the data-set looked rather small. Therefore I suggest to check the data-model if all associations between the tables are properly working - if not it might creating any cartesian product which is then forcing your memory error.