Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Preceding Load Performance

Hello, i have read

Preceding Load

and https://www.quickintelligence.co.uk/preceding-load-qlikview/ but i still have some dubts about preceding load. Is this:

Load  ..., ReferenceDate,

   Age( ReferenceDate, BirthDate ) as Age;

Load  *,

   Date( FromDate + IterNo() – 1 ) as ReferenceDate

   Resident Policies

      While IterNo() <= ToDate - FromDate + 1 ;

Is faster than This:


TmpTable:

Load  *,

   Date( FromDate + IterNo() – 1 ) as ReferenceDate

   Resident Policies

      While IterNo() <= ToDate - FromDate + 1 ;

Table:

Load  ..., ReferenceDate,

   Age( ReferenceDate, BirthDate ) as Age

From TmpTable;

And Why. So It's preceding load doing some kind of shortcut or just a way to to don't have the need to have lots of temp tables when you do calculations like flags etc.

12 Replies
olivierrobin
Specialist III
Specialist III

i've also noticed a point (and retested just now)

if you do a preceding load, you loose the optimized load of a qvd

so in this case, it's better to do 2 load : 1 optimized from qvd, one from resident

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

In the case of a preceding load, I found reloading from a QVD significantly faster than a Resident load. 2-3 times faster. I have test data going all the way back to V9.

In the Nov 2017 QV release, things have changed.  I believe the bugfix that Henric mentioned was released.  Testing against that release shows resident is now faster than qvd. Multi-processing is back!

The really excellent news is that I no longer see any penalty in using preceding load.  I'll do some more extensive testing and get a blog post out next week.

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP