Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

maleksafa
Valued Contributor

Re: Optimized load

but that's very weird for an optimized load, because if i load the qvds the other way around, only one of them will be optimized but the overall load time will be much faster.

Highlighted
MVP
MVP

Re: Optimized load

That is probably because, qv takes more time to resturcture a table than this unoptimized load. I did not test it, still it seems that this case (loading your second your table fast) would only be faster iff the second table is a subset of the first one. Because, that would lead not restructure the first table.

Highlighted

Re: Optimized load

Malek

What you need to do is when you create the 2 source qvd's, add the extra fields in with values of null.  Such that both your input qvd's have the same structure.

This was recommended to me by stevedark and I have used it and it works perfectly for me.

Highlighted
maleksafa
Valued Contributor

Re: Optimized load

i will give it a try, but adding null fields to the second load will make it not optimized, so i guess it is a compromise to take between optimized load and this.

Highlighted

Re: Optimized load

Malek

That was not what I meant.

What I meant was when you create the 1st source qvd add the fields as Null's that are in the 2nd qvd but not this 1st qvd.

Then when you create the 2nd source qvd add the fields as Null's that are in the 1st qvd but not this 2nd qvd.

Such that both the resulting 1st and 2nd qvd 's have identical structures.

Highlighted
MVP & Luminary
MVP & Luminary

Re: Optimized load

Thanks for the mention Bill.