topic binary incremental load in QlikView

binary incremental load

Thu, 01 May 2014 09:09:52 GMT

Hi does anyone have knowledge how to setup binary incremental load? I have read that it is much faster then regular qvd incremental load.

So instead of keeping historic data in QVD it only contains the incremental loaded data.

Hope someone can help

Thanks in advance

Re: binary incremental load

swuehl — Thu, 01 May 2014 09:12:07 GMT

Not sure what you mean with binary incremental load, you can only perform a single binary load in your script.

Could you reference where you have read about this, so to give context?

Re: binary incremental load

Thu, 01 May 2014 09:15:57 GMT

Yes of cause :

http://www.qlikviewaddict.com/2012/02/power-of-binary.html

I have a problem with that when i reduce and distribute my qlikview document it takes over 8 hours (and the file only consists of 50 mil rows) So it really shouldnt take that long.

But i cannot seem to figure out why its so slow

Re: binary incremental load

Colin-Albert — Thu, 01 May 2014 09:22:00 GMT

The binary command loads all data from one QVW into another.

To add the delta data for an incremental load, you would need to be able to identify the most recent records in the tables loaded in the binary command and then append new data to those tables in your load script.

This should be straightforward if the delta simply consists of new data, but will become more complex if you need to handle deleted / modified records and slowly changing dimensions.

Re: binary incremental load

Colin-Albert — Fri, 02 May 2014 06:18:55 GMT

Which version of QV server are you using? Ver 11.0 changes in the way documents are opened for distribution which may affect your performance.

Re: binary incremental load

Fri, 02 May 2014 07:30:02 GMT

I use Version 11.20

Re: binary incremental load

Peter_Cammaert — Fri, 02 May 2014 09:51:44 GMT

In the affected document, can you pinpoint where exactly this excessive amount of time is wasted? Or is it the Reduce step itself? (in that case the document log should show speedy execution, but the task log will show a big delay somewhere)