What is optimised QVD? - Qlik Community

It's the manner of LOADing them that can be optimlized aka extremely fast. This usually means omitting any WHERE clauses, or using WHERE Exists() clauses with only one parameter. As long as you load columns as they are (no expressions), the LOAD stays optimized as well. Simply renaming fields is allowed too.

As soon as you use more complex column expressions or WHERE clauses, or you CONCATENATE or JOIN a QVD, the LOAD becomes un-optimized.

Peter

Report Inappropriate Content · ‎2015-01-31

Hi,

Loading the data from DB into QVD without performing any transformations is Optimized Load.

Load * from table;

Loading the data from DB into QVD with some transformations.

Load * from table where Year=2015;

Colin-Albert · ‎2015-01-31

Sorry Chiranjeevi, but your answer is incorrect.

An optimized QVD load only happens when you load data FROM a qvd file into your application, and there are no data transformations or a single "where exists" clause. This can be seen in the reload progress window.

Loading from QVD files where the data is transformed, joined to other tables or other where conditions are used will not be optimised, so will load slightly slower, but faster than reloading the same data from the original source files.

You can only have a load flagged as optimized when loading from QVD files not from databases or other files.

Anonymous · ‎2015-01-31

Hi,

Optimized load is much faster and therefore preferable, especially for larger data sets. Optimized QVD loads are up to 100 times quicker than non-optimized ones.

Optimized loads are possible if no transformations (calculations) are made during the load, and no (almost) filtering is done in a WHERE clause. The only acceptable filter is using function Exists: WHERE Exists (Field)

So for example this load can't be optimized: Load * From ... WHERE Country = 'US'

But this load can be optimized: Load * From ... WHERE EXISTS (Country)

For Qlikview version 10 and earlier, the only time you want the load not to be optimized, is if you load a Mapping table from a QVD file. In this case, Optimized load doesn't quite work, so you want to make the load non-optimized deliberately.

There is no concept of Optimized QVD, the qvd just has data stored in it. There is a concept of Optimized QVD load, it is the one which loads the data in QVD as such without any transformation, filtering etc.

See below links

http://www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/

Optimized .QVD Confusion

http://www.citagus.com/citagus/blog/optimized-qvd-loads-in-qlikview/

Regards

Neetha

maxgro · ‎2015-01-31

Optimized / non optimized refers to the load of qvd, not to the file

Optimized is (usually) faster

When you reload you can see in the script execution progress window if the load is optimized

testqvd 10.000.000 lines fetched

testqvd (qvd optimized) 10.000.000 lines fetched

this is from http://www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/

(thanks to Steve Dark)

"

Some examples of things that will cause a non-optimised load are:

- Adding new fields to the table
– Deriving new values from a field in the QVD
– Retrieving a field twice
– Most WHERE conditions
– Joining to an existing in memory table
– Loading data into a mapping table

In contrast the things you are allowed to do are:

- Rename fields

– Omit fields
– Do a simple one field WHERE EXISTS on a field returned in the record set

"

Report Inappropriate Content · ‎2015-02-02

simply u can say

if u are doing all transformations while creating qvd that is qptimized qvd.

if u are doing all transformations while loading data from qvd to qvw then it is unoptimized qvd