what are functions we are using in optimized qvd ? and non optimized? urgent...

[#1]

what are functions we are using in optimized qvd ? and  non optimized? urgent...

[fkeuroglian]

Please, explain better or put and example about what is exactly your question

[#3]

during optimizig what are functions we can use and during non optimizing what are functions we use

[Anonymous]

refer to QVD Files in the help section.

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.

[maxgro]

exists with 1 parameter  for optimized load

for detail see here

EXIST while loading QVD

[amit_saini]

Hi Manoj,

Optimized load is much faster and therefore preferable, especially for larger data sets.

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:

Load * From ... WHERE EXISTS(Country)

================================

On the other hand, 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.

Thanks,

AS

[#7]

optimized load is possible when reading from QVD

renaming any column

and simple where condition can create optimize way of reading from QVD