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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
sreeni_qvd
Creator
Creator

Create datamodeling


Hi All,

Please find the attached data source and create data modeling and explain to this was correct data modeling.

Thanks&Regards:

Sreeni 

5 Replies
datanibbler
Champion
Champion

Hi Sreeni,

I'm sorry, but I do not quite understand, are you asking for help with anything? If yes, what is your requirement?

Best regards,

DataNibbler

sreeni_qvd
Creator
Creator
Author

Hi DataNibbler,

I gave sample data, I created one QVW for data modeling, PFA and let me this is correct or not.

Regards

Sreeni

sreeni_qvd
Creator
Creator
Author

Hi,

PFA , Please let me this was correct data modeling or not.

PFA data source.

datanibbler
Champion
Champion


Hi Sreeni,

yes, you created a document, I had a look at that. Maybe you could instead attach your qvw to this discussion? That would make it somewhat easier.

Well, your data_model looks good enough to me - the "ideal" recommended star-shape or snowflake-shape cannot always be kept - yours would probably categorize as a "snowflake-shape" as you have one primary central table (which most of your data_tables are linked to) and one "secondary central table", from which there are links to several data_tables.

The important things about the data_model are:

- Avoid synthetic keys (you haven't got any at the moment)

- Avoid loose tables (circular references)

- Avoid "data islands" (tables which are not linked to any others) as these are extremely resource-heavy.

=> The tool of choice (to force and to break QlikView's automatic links) is renaming (the >as< option)

=> Also important is the quality of keys. You can read up on "information density" and such, but as a rule of thumb

- "perfect key" and "primary key" means a key is sufficient to uniquely identify every single record

   => That should always be the case in masterdata_tables

HTH

Best regards,

DataNibbler

P.S.: The bottom line, if there was any, might be: If your data_model works for you, it's fine for the moment. You'll get ideas to make it even better and slimmer as you go along.

sreeni_qvd
Creator
Creator
Author

Thank you.