diffrence b/w optimized load and unoptimized load

Wed, 19 Feb 2014 11:56:26 GMT

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

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

Re: diffrence b/w optimized load and unoptimized load

Gysbert_Wassenaar — Wed, 19 Feb 2014 12:00:29 GMT

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

Re: diffrence b/w optimized load and unoptimized load

IAMDV — Wed, 19 Feb 2014 12:08:19 GMT

Re: diffrence b/w optimized load and unoptimized load

MK_QSL — Wed, 19 Feb 2014 12:17:37 GMT

optimize and non-optimze load in qvd

Re: diffrence b/w optimized load and unoptimized load

er_mohit — Wed, 19 Feb 2014 12:28:39 GMT

1) Optimized and unoptimized QVD Load Situations?
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.

e.g. All Loads are optimized

Table:

LOAD // Optimized

FROM Table1.qvd (qvd);

CONCATENATE(Table) // Optimized

LOAD

FROM Table2.qvd (qvd);

e.g. 2nd Load isn't optimized

Table:

LOAD // Optimized

FROM Table2.qvd (qvd);

CONCATENATE(Table) // Not optimized

LOAD

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)

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

see the attached pdf also

For different types of load go to this link

Different ways to load data in to Qlikview

Re: diffrence b/w optimized load and unoptimized load

Sun, 01 Jun 2014 11:14:29 GMT

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

Re: diffrence b/w optimized load and unoptimized load

jagan — Sun, 01 Jun 2014 12:18:08 GMT

Hi,

Check this document

Optimized and Non Optimized loading

Regards,

Jagan.

topic Re: diffrence b/w optimized load and unoptimized load in QlikView

diffrence b/w optimized load and unoptimized load

Re: diffrence b/w optimized load and unoptimized load

Re: diffrence b/w optimized load and unoptimized load

Re: diffrence b/w optimized load and unoptimized load

Re: diffrence b/w optimized load and unoptimized load

Re: diffrence b/w optimized load and unoptimized load

Re: diffrence b/w optimized load and unoptimized load