
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
diffrence b/w optimized load and unoptimized load
what type of loads are their in qlikview? and briefly...
what is the diffrence between optimized load and unoptimized load? in qlikview
- Tags:
- new_to_qlikview
- subbu

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
See this blog post: www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/
talk is cheap, supply exceeds demand

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also read this post:
http://qlikviewnotes.blogspot.co.uk/2011/02/qvd-questions-and-answers.html

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 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
A,
B,
C
FROM Table1.qvd (qvd);
CONCATENATE(Table) // Optimized
LOAD
A,
B,
C,
D,
E
FROM Table2.qvd (qvd);
- 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 2nd 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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
