topic Re: Best Practice for Implementing Incremental Reload. in QlikView

Best Practice for Implementing Incremental Reload.

rob_insley — Sun, 02 Nov 2014 21:29:52 GMT

I am supporting an implementation of Qlikview where the End Application contains a Load Script which uploads Incremental data to the data model. The reload schedule of this document is every 20 minutes and the load scripts takes between 9-11 minutes to complete.

When the reload schedule is running then the performance the users experience is considerably worse than when it is not running. Is there an established best practice in terms of :

a) Incremental Reload methodology when reloading a document accessed by users

b) Document Settings

c) Server settings

that would minimise the impact of high frequency reloads on end user performance.

Any advise or pointers gratefully received.

Thanks

Re: Best Practice for Implementing Incremental Reload.

rob_insley — Sun, 02 Nov 2014 21:35:43 GMT

I should add that there is no Publisher Server in this solution, only Qlikview Server and all processes are running on a single server.

Re: Best Practice for Implementing Incremental Reload.

ashfaq_haseeb — Mon, 03 Nov 2014 05:19:50 GMT

Hi,

Check this for better understanding.

Regards

ASHFAQ

Re: Best Practice for Implementing Incremental Reload.

amit_saini — Mon, 03 Nov 2014 05:35:40 GMT

Rob,

Please see the attachments.

Thanks,

Re: Best Practice for Implementing Incremental Reload.

sakamsureshbabu — Mon, 03 Nov 2014 05:41:31 GMT

i have this same problem

Re: Best Practice for Implementing Incremental Reload.

vardhancse — Mon, 03 Nov 2014 05:48:08 GMT

Convert the data in to QVD, so that for every dashboard maintain one QVD geerator app and one main dashboard file.

So that while QVD generetor was running there will be no impact for dashboard to uses.

Once QVD generator was completed then we can reload main dashboard file.

Re: Best Practice for Implementing Incremental Reload.

sakamsureshbabu — Mon, 03 Nov 2014 06:22:36 GMT

thanks