Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Data Model Forced Concatenate

Hi Guys,

I have scenario like this i haver two transaction tables Transaction and Sub Transaction both have diffrent facts only  4 facts are same

one fact table is having 20 facts and another is having 28 facts , so i want to know should i keep my two fact tables seprate or i should use Forced concatenate

so asd to have a star schema model. what if i keep two fact tables seprate does it dont go down well in terms of qlik view best practises.

Thanks in advance,

Anant

Labels (1)
2 Replies
Anonymous
Not applicable
Author

For simplicity I would try concatenating them and checking on the performance.

It's tough to say what works best between a concatenated fact table and a link table model as I've seen both outperform the other for different scenarios (although a concatenated model is often easier to create from a modelling perspective).

Try both ways and do some performance testing to get the appropriate response for your scenario.

Not applicable
Author

Thanks Johanees !