Qlik Community

New to QlikView

Discussion board where members can get started with QlikView.

Announcing the newest addition to the Qlik Community, Qlik Gallery! Learn More
Contributor II

how to reload the Qvd file

Hi experts,

I have the following scenario.

I have designed the dashboard in the canvas (QVW File 1 ) by loading the data from QVD.

2nd QVW file (QVW File 2 ) i have used to load the data from database to QVD.

Now , when i refresh the canvas will the Qvd Data hit the database and get the records ???

or will it just hit the data which is already loaded into the QVD File ??

Please clarify on this.

If the Canvas is not hitting the database through QVD and just hitting the loaded data in QVD. how should this be handled??

i want the Canvas to hit the database through the QVD Called to fetch the data.

PLease Help!!!!


4 Replies
Esteemed Contributor

Re: how to reload the Qvd file


so here:

1st step: you load data from DATABASE to QVD

2nd step: you load QVD's on the last app which is your DASHBOARD

on your first step, you should use an incremental load, to load the old QVD and concatenate on it the new lines from your Database and create a refreshed QVD.

the technique is decribed here:


Contributor II

Re: how to reload the Qvd file

Thanks for your immediate response Youssef.. Will definitely try this out.

Esteemed Contributor

Re: how to reload the Qvd file

you're welcome ! try it and let me know

Re: how to reload the Qvd file

On average, a QlikView setup works the other way: for updating a QVW document in a reliable way, you start by getting fresh data from your data sources by running QVW2. If and when that action is successful, you can trigger your end-user facing dashboard to reload itself from the updated set of QVD files. If the reload of QVW2 wasn't successful (for whatever reason), the Dashboard shouldn't move and keep displaying the old data set.

By using this sequence, you can

  • guarantee your end-users that something consistent is shown in the dashboard
  • make sure that and end-user doesn't have to wait for a sequence of reloads to finish, because all of this usually happens behind the scenes (if you're publishing your documents on a QlikView Server)

In a Qlik world, end-users do not often trigger reloads. The server does that, and at specific controlled points in time only.