Qlik Community

New to Qlik Sense

Discussion board where members can get started with Qlik Sense.

Announcements
QlikWorld 2020: Join us May 11 - 14, 2020 in Phoenix, AZ. Register early and save $400. Learn More
IPPSA-DMT-OA
New Contributor

Data Reload and Processing Burden

Hello!

From reading some of the documentation and conversations on the forum, my current understanding of the Qlik sense data consumption process is that Qlik loads data from "inputs" such as spreadsheets, raw in-line, databases, etc.. and then aggregates the data, compiling it into a QVD file for processing within Qlik.

Since there is no automatic data "binding" between Qlik and its data sources, it seems that the common solution is to utilize a fixed interval reload (which I understand to be an enterprise feature with a maximum frequency of 1 reload / 24 hrs).

Does this mean that the data presented to the end users will remain completely static until the scheduled reload each day?
Would it be possible for me to write a custom service to force a manual reload at whatever time-interval I desire?

Secondly, who bears the burden of holding data and executing the filter logic?
Does each client receive data and is the processing burden borne by the client?
Or does the server retain the data, process (filter / format) it, and just pass the view to the client?

Does the paradigm change when using Qlik vanilla-style versus embedding it via JS API / iFrame URL API?

Apologize if these questions are off base. My organization recently purchased Qlik, and this is my first exposure to the application.

1 Solution

Accepted Solutions
Partner
Partner

Re: Data Reload and Processing Burden

Regarding first question

Qlik is an in-memory BI tool which means all data as you rightly suggest is withing the app (you can say static ). it wont refresh until you reload.  advantage to in-memory tool is quick response times because no db queries execute everytime user selects a filter

Your reload schedule understanding is not correct. it can be made hour, daily, monthly ,  dependent on another qlik reload task as well

 

regarding q2

out of the box all processing is done on the server and details for rendering visualization is passed onto the client browser. 

View solution in original post

3 Replies
Partner
Partner

Re: Data Reload and Processing Burden

Regarding first question

Qlik is an in-memory BI tool which means all data as you rightly suggest is withing the app (you can say static ). it wont refresh until you reload.  advantage to in-memory tool is quick response times because no db queries execute everytime user selects a filter

Your reload schedule understanding is not correct. it can be made hour, daily, monthly ,  dependent on another qlik reload task as well

 

regarding q2

out of the box all processing is done on the server and details for rendering visualization is passed onto the client browser. 

View solution in original post

IPPSA-DMT-OA
New Contributor

Re: Data Reload and Processing Burden

Thank you for your response and clarification!

Partner
Partner

Re: Data Reload and Processing Burden

No problems. Happy to help