topic QVD Advantages in QlikView

QVD Advantages

Fri, 02 Oct 2015 13:56:43 GMT

Hi Experts,

I am new to Qlikview. I want to know about QVD and advantages. Please explain in simple way.

Thanks in Advance

Re: QVD Advantages

Gysbert_Wassenaar — Fri, 02 Oct 2015 15:58:26 GMT

See this blog post: http://www.quickintelligence.co.uk/qlikview-qvd-files/

Re: QVD Advantages

Fri, 02 Oct 2015 16:04:09 GMT

In a nutsehell, they are encrypted, condensed/compact files athat only Qlikview can read. Since they are a proprietary format, other applications cannot access them but it allows qlikview to read a lot of data very efficiently.

further details provided in articed

Re: QVD Advantages

Anonymous — Fri, 02 Oct 2015 16:05:58 GMT

QVDs in Qlikview | Learn QlikView

Regards.

Re: QVD Advantages

Anonymous — Fri, 02 Oct 2015 16:07:34 GMT

Hi Abhi,

A QVD (QlikView Data) file is a file containing a table of data exported from Qlik Sense. QVD is a native Qlik format and can only be written to and read by QlikView. The file format is optimized for speed when reading data from a script but it is still very compact. Reading data from a QVD file is typically 10-100 times faster than reading from other data sources.

Advantages:

Increasing load speed :

By buffering non-changing or slowly-changing blocks of input data in QVD files, script execution becomes considerably faster for large data sets.

 Decreasing load on database servers :

The amount of data fetched from external data sources can also be greatly reduced. This reduces the workload on external databases and network traffic. Furthermore, when several scripts share the same data, it is only necessary to load it once from the source database into a QVD file. Other apps can make use of the same data through this QVD file.

 Consolidating data from multiple apps :

With the binary script statement, data can be loaded from a single app into another app, but with QVD files a script can combine data from any number of apps. This makes it possible for apps to consolidate similar data from different business units, for example.

 Incremental load :

In many common cases, the QVD functionality can be used for incremental load by only loading new records from a growing database.

Hope it helps!!

Re: QVD Advantages

Peter_Cammaert — Fri, 02 Oct 2015 16:08:33 GMT

Let me widen that statement a bit. Not only QlikView can read QVDs, any tool that uses a Qlik OEM SDK is able to read QVDs. There are a lot of QVD viewers on the market.

Therefor the "encryption" is in no way helpful in securing the data in a QVD.

Peter

Re: QVD Advantages

qlikviewwizard — Fri, 02 Oct 2015 17:00:40 GMT

Hi abhiram0616,

Please read this:

One of the things that new developers often ask about QVDs is, "why?". They wonder

why they need to use QVDs. They know that they can connect to a database and read

data and they feel that they can do that again and again and don't see any reason why

they need to bother writing the data to a QVD file first. There are, however, several

very good reasons to store data in QVDs:

• Speeding up loads by storing data that doesn't change, or doesn't change

very frequently. Loading data from a database is relatively much slower

than loading data from a local QVD. For example, if you have 2-year-old

transactions, that won't change; you could have those in QVDs, and then

load newer transactions from the database and concatenate the two sets of

data. Of course, this also reduces the load on the database server because

we are only looking for relatively few rows of data on each SQL call.

• Combining data from multiple different sources. For example, we could have

a new ERP system in place but we also want to add in sales information from

an old system. If we keep the old data in QVD, we don't need to have the old

database online, so it can be decommissioned.

• Incremental load is the ultimate use of QVDs to load transactional information

in the minimum amount of time possible. Basically, we load only the newest

data from the database, combine with the older data from locally stored QVDs,

and then update the QVDs.

•QlikView Data Modeling, dimensional modeling

approaches say that we should use conformed dimensions where dimensions

are shared across different models. This is an excellent use of QVDs—we

create the QVD once and then can share it across many QlikView documents.

Even if we are not following a strict dimensional modeling approach, we can

still use QVDs to reuse data in more than one application.

• Implementing data quality when preparing data for users. A cleaned set of

QVD files, that are centrally created and controlled, can be provisioned for

users with confidence that data is correct.

Just from a development point of view, you will find that you are performing reloads

again and again as you are perfecting your data model. If you are reloading from a

slow database connection, this can be painful. If you create local QVDs, then your

development efforts will proceed a lot faster.

Courtesy - Mastering Qlikview Book

Re: QVD Advantages

hic — Fri, 02 Oct 2015 18:02:25 GMT

There are only two advantages:

Better load speed
They can be prepared to contain dual values, so that dates and other fields don't need to be interpreted when the files are loaded.

The other above mentioned advantages can be achieved also by loading from text files.

The QVD files are not encrypted.

HIC

Re: QVD Advantages

Sun, 04 Oct 2015 11:53:21 GMT

Thank You all for sharing knowledge

Re: QVD Advantages

qlikviewwizard — Sun, 04 Oct 2015 11:56:52 GMT

Hi Abhi,

Just a thought. Why don't you create a snippet and post as a document? It will be very useful for our community folks.

Re: QVD Advantages

Nagaraju_KCS — Sun, 04 Oct 2015 12:09:57 GMT

Hi Abhi,

A QVD file is a native QlikView file format optimized and compacted for speed when reading data from within a QlikView load script. Reading data from a QVD file can be 10-100 times faster than reading records directly from other data sources. A QVD file contains a single table of data from a QlikView application. While that may seem somewhat restricting remember that table can be the result of a concatenation or a join so the structure you create in the application can greatly increase its use. You can also include all calculations and manipulations in the script that creates you QVD file further increases load performance at run time.

There are several uses for a QVD file and in many cases more than one will be applicable at the same time.

• Decreasing Load Time

• Decreasing Database Server Loads

• Joining Data from Different QlikView Applications

• Incremental Data Loading