topic Data Model Forced Concatenate in QlikView

Data Model Forced Concatenate

Fri, 09 Nov 2012 08:04:43 GMT

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

Re: Data Model Forced Concatenate

Anonymous — Fri, 09 Nov 2012 14:57:33 GMT

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.

Re: Data Model Forced Concatenate

Fri, 16 Nov 2012 11:39:15 GMT

Thanks Johanees !