REF : QlikView 11 for Developers....
Dear Vishal,
Finding a balance
We have outlined two ways for dealing with multiple fact tables in a data model. If we were
to ask which of these methods is better, we would need to say, again, "it depends." There
is no definite best, and the decision about which to use will depend entirely on the specific
scenario where it has to be implemented.
When deciding on data model design, you should always ask yourself if the "structural
asymmetry" we talked about before is something you could accept in your data model, or if
the asymmetry is highly significant and therefore you would prefer to live with the "additional
hop" in the data model.
Choosing between approaches can also impact the application's size. Take a look at both
of the files created using each of the preceding methods and see which one is smaller in
disk size .Can you guess why the link table approach produces a smaller file? It's because
we've taken out some fields from the relatively large fact tables and placed them into a
smaller link table.
For QlikView, both of these approaches are OK. They work as they should and there
should not be calculation differences resulting from using them one over the other.
