topic Non-optimize load in QlikView

Non-optimize load

rapovets_A2C — Sat, 16 Nov 2024 20:40:36 GMT

Hi everybody
I can not understand because of what is non-optimize loading gvd files

the example in the attachment

Re: Non-optimize load

Nishanthi — Thu, 13 Jun 2019 09:43:15 GMT

Non-Optimize refers to loading of data as it is. For example,

Load

from table;

Optimize refers to loading of data by applying some transformations. To put it in a simple way by using a where clause you refine the load in an optimized way rather than loading all the data which will not be used. For example,

Load

from table where A>10;

Re: Non-optimize load

rapovets_A2C — Thu, 13 Jun 2019 10:07:57 GMT

Where exists allows optimize load

Re: Non-optimize load

Nishanthi — Thu, 13 Jun 2019 09:47:26 GMT

Whatever condition you give after where clause is optimized load.......

Re: Non-optimize load

rubenmarin — Thu, 13 Jun 2019 10:09:01 GMT

Hi, Exists() is only optimized in the one parameter version: Where Exists(FieldName)

Check if you can make it work using same field names to avoid the 2 parameters version fo Exists().

Re: Non-optimize load

jerrysvensson — Thu, 13 Jun 2019 10:10:54 GMT

Where exist() with same field name will be optimized.
But where exists(field1, field2) will be unoptimized. As in your code.

Re: Non-optimize load

rapovets_A2C — Thu, 13 Jun 2019 10:40:53 GMT

in my code these are identical fields
goods:
load
Field1
from goods.qvd(qvd);

Sales:
load
date,
field2
from Sales.qvd(qvd)
where Exists(field1,field2);

this is optimized load

Re: Non-optimize load

rubenmarin — Thu, 13 Jun 2019 10:48:54 GMT

In that case goods is optimized but not Sales. A workaround to make both tables optimized can be

goods:
load
field1,
field1 as field2
from goods.qvd(qvd);

Sales:
load
date,field2
from Sales.qvd(qvd)
where Exists(field2);

drop field field2 from goods;

Re: Non-optimize load

Brett_Bleess — Tue, 16 Jul 2019 16:07:19 GMT

Just adding a Help link in case you still need some further explanation to get things to make complete sense here:

QVD files can be read in two modes: standard (fast) and optimized (faster). The selected mode is determined automatically by the QlikView script engine. Optimized mode can be utilized only when all loaded fields are read without any transformations (formulas acting upon the fields), though the renaming of fields is allowed. A WHERE clause causing QlikView to unpack the records will also disable the optimized load. An optimized .qvd is extracted and handled according to standard Extract-Transform-Load (ETL ) when a field transformation is performed, this results in a degradation of performance. The specified format will not be maintained and the underlying raw number format will be used instead and recognized. Transformations of the field in a .qvd is allowed, the former "Optimized" .qvd then becomes a standard non-optimized .qvd.

That is from here: http://help.qlik.com/en-US/qlikview/12.1/Subsystems/Client/Content/QVD_files.htm

Regards,
Brett