Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I read about QVD and it says a lot.
But when I do the reload CTRL+R. The same time is taking to fetch the data. Then why we have to use QVD. Am I doing anything wrong?
Example:
Table 1
Load
a
b
c
SQL Select *
From 123 table;
Store Table 1 into c:\.....qvd;
Now QVD is created.
Then I am loading
Load *
From QVD;
What is the benefit?
If I reload the Table 1 will be queried and it will store the data in to QVD.... then
There is plenty of Difference when you travelling 10KM distance by walk and Car. So its depends on your data size.
-Jay
Jay - my doubt is I loaded the original table in to qlikview say Table 1 and I have a QVD file.
Do I have to load the QVD file in the same QVW. If yes then I will be having 2 tables right. original table and data from QVD table.
I am confused
Hi Vijay,
You have to use either QVD or DB. Its depends on your requirement. QVD will act like bridge between your application and DB
When ever DB updated with new record you can refresh QVD creation file and your final App.
-Jay
If you are working within the same document, you won't need to use QVDs, you can use resident load to use an already loaded table.
Hi Vijay,
QVDs are used to store the data from database / Datasource tables. A QVD can hold information of one DataSource table.
Generally QVDs are used to reduce the load on database servers. For example if you have a table called Product, which is been used in almost all Dashboards then for the first time the Customers information is fetched from the Datasource and save it in the QVD. After that the data in the QVD is used to load the Customer information in all Dashboards. This way we will reduce the load on database.
For example if we have 10 Dashboards, we are only hitting the database 1 time the other 9 times we are using QVD to load the data.
Also QVDs are the only way to implement the incremental loading in Qlikview.
Hope this helps you.
Regards,
Jagan.