diffrence b/w optimized load and unoptimized load

[#1]

what type of loads are their in qlikview? and briefly...

what is the diffrence between optimized load and unoptimized load? in qlikview

[Gysbert_Wassenaar]

See this blog post: www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/

[IAMDV]

Also read this post:

http://qlikviewnotes.blogspot.co.uk/2011/02/qvd-questions-and-answers.html

[MK_QSL]

optimize and non-optimze load in qvd

[er_mohit]

1. 1)      Optimized and unoptimized QVD Load Situations?
2. Ans. When concatenating two tables that don't have the same number of fields, if the second table has the same fields than the first one and then some extra fields the load will still be optimized, if done the other way around it will not be optimized.

1. e.g. All Loads are optimized

Table:

LOAD // Optimized

     A,

     B,

     C

FROM Table1.qvd (qvd);

CONCATENATE(Table) // Optimized

LOAD

     A,

     B,

     C,

     D,

     E

FROM Table2.qvd (qvd);

1. e.g. 2nd Load isn't optimized

Table:

LOAD // Optimized

     A,

     B,

     C,

     D,

     E

FROM Table2.qvd (qvd);

CONCATENATE(Table) // Not optimized

LOAD

     A,

     B,

     C

FROM Table1.qvd (qvd);

Or   2^nd Ans. Is

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.

Another Answer For Optimize and Non- Optimized

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.

see the attached pdf also

For different types of load go to this link

Different ways to load data in to Qlikview

[#6]

Hi Subbu

There are some restrictions toward optimised load

Please see the link below

Optimized and unoptimized QVD Load Situations? thanks in advance

Regards

Padma

[jagan]

Hi,

Check this document

Optimized and Non Optimized loading

Regards,

Jagan.