Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
The faulty results are a result of the incorrect data model.
so my question are as per below,
while designing data modelling what to consider while linking the table.
Is information density and subset ratio helps to create perfect data model.
Or only joining primary key and foreign key will be enough for joining the table and getting perfect results.
Thanks
This post may help you:
Hi jacob,
Can you please give me an overview abt this.
Thanks
Hi,
Some few principles
1. Defined requirements i.e. what should be achieved
2. Data volume and complex relationship with many data linkages
3. Avoid circular reference and complex synthetic keys
4. Long calculations in chart i.e. calculations that include different dimensions from different tables for example
5. Since QlikView perform well with de-normalized datamodel, strive if possible, to use a STAR data model as opposed to SNOWFLAKE model
Check Qlikview documantation as well.
Thanks.
Hi, try to read this
http://www.quickintelligence.co.uk/perfect-your-qlikview-data-model/
and then get a conclusion about the model and the decision
Good luck
Fernando
1. Only load columns and rows that you will use in your qlikview app.
2. Avoid synthetic keys (two or more fields appearing in the same tables)
3. Avoid circular logic (more than one way to connect two tables)
4. Consider using QVDs to optimize reloading