topic Re: Forced or Non Forced Concatenation? in QlikView

Forced or Non Forced Concatenation?

helen_pip — Fri, 06 Dec 2013 09:15:15 GMT

Hello

I am looking for some advice as to what method is more efficient (Best practice) for the server and the front end user

1) I have 4 QVW's each of which have 5 QVD's concatenated within. All QVD's have the exact same field names

The 4 QVW's are scheduled and take between 1-5 minutes to run each

4 QVW's running on the scheduler

2) I have 1 QVW each of which have the 20 QVD'S concatenated within. I am now using forced concatenation as not every QVD has the same field name.

The QVW is scheduled and takes 1 hour 9 minutes to run

1 QVW running on the scheduler

In addition I have 1 final QVW. Which will either have a further concatenation of 4 QVD's (Option 1) or 1 QVD (Option 2)

Does anyone have any advice?

Many Thanks

Helen

Re: Forced or Non Forced Concatenation?

swuehl — Fri, 06 Dec 2013 10:20:16 GMT

It looks more like a question of unoptimized vs optimized load (the forced concatenation enforces an unoptimized load).

You are not doing any other transformations in your qvws when loading from your qvd's, right?

If that's the issue, it may result in almost the same time needed either way. But, why don't you just test it?

To avoid the forced concatenation / unoptimized load, you could consider storing your qvds all with the same field names when creating the qvds, some fields just having NULLs.

Re: Forced or Non Forced Concatenation?

helen_pip — Fri, 06 Dec 2013 10:53:04 GMT

Hello

Thank you for your advice. I am going to test and try considering Null values in the fields

Thanks

Helen