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

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Kindly help me in my data model

Dear Friends,

I appreciate your time.

I have 1 fact and 3 dimension say dim1,dim2,dim3 tables. Fact and dim1 table are connected via key1 and having 4 fields repeating with same values between fact and dim1 table say field1,field2,field3,field4. Shall I remove those from fact table and keep in dimension only.

Is it a good practice?

Kindly share your ideas!


Thank you !

Jeevi

4 Replies
hector_munoz
Specialist
Specialist

Hi Jeevi,

Yes I think you only should keep fields in master tables, not in fact tables. In fact tables only key fields and fact fields such as sales, revenue, margin, etc.

Is a clearer model and a more optimal too.

Regards,

H

Not applicable
Author

Hi,

Thank you so much for your time. I sincerely appreciate it.

Actually field3 and field4 is linked to other  tables.

eg:

Table(Fact) : CustNo,CustName,TerritoryNo,UnionNo,Amount

Cust Table :  CustNo,CustName,TerritoryNo,UnionNo,Addr,Pin

TerritoryTable : TerritoryNo,TerritoryName

UnionTable:     UnionNo,UnionName

could you kindly let me know the best way to create my data model.

If I need to keep it as a STAR Schema, I need to keep TerritoryNo,UnionNo in Fact Table or put everything in Customer table and make it as a Snow Flake. But STAR Schema  is the best approach for any data set (mine with some 50,000 rows) in a Excel file. Kindly let me know.

Thank you again!

Jeevi

hector_munoz
Specialist
Specialist

Hi Jeevi,

In that case, in Table(Fact) I would remove CustName as it is in Cust Table, and in Cust Table I would remove TerritoryNo and UnionNo fields, for having a star model:

Table(Fact) : CustNo,TerritoryNo,UnionNo,Amount

Cust Table :  CustNo,CustName,Addr,Pin

TerritoryTable : TerritoryNo,TerritoryName

UnionTable:    UnionNo,UnionName

Anyway if you only have those fields and 50K rows you could also try an only one table model with the join of all fields.

I attach you a Qlik document about these topics...

Hope ir serves!

Regards,
H

vinieme12
Champion III
Champion III

Buddy, it'll much easier for people here to help you if you post some sample data that best replicates your scenario

Vineeth Pujari
If a post helps to resolve your issue, please accept it as a Solution.