{"id":38598,"date":"2018-11-18T10:00:18","date_gmt":"2018-11-18T04:30:18","guid":{"rendered":"https:\/\/data-flair.training\/blogs\/?p=38598"},"modified":"2021-12-07T11:20:12","modified_gmt":"2021-12-07T05:50:12","slug":"best-practice-for-data-modeling-in-qlikview","status":"publish","type":"post","link":"https:\/\/data-flair.training\/blogs\/best-practice-for-data-modeling-in-qlikview\/","title":{"rendered":"Best Practice for Data Modeling in QlikView – 11 Unique Practices"},"content":{"rendered":"

The last session ends on QlikView Data Types<\/strong>. Here, we will talk about the importance of Data Modeling in QlikView.<\/p>\n

Moreover, we will learn the Best Practice for Data Modeling in QlikView with their examples.<\/p>\n

So, let’s start the tutorial of “Best Practice for Data Modeling in QlikView”.<\/p>\n

\"Best<\/a>

Best Practice for Data Modeling in QlikView – 11 Unique Practices<\/p><\/div>\n

Importance of QlikView Data Modeling<\/h3>\n

A good data model ensures the\u00a0efficient working of your application in QlikView<\/strong>. <\/span><\/span><\/span><\/p>\n

This means, the data will process faster, expressions will evaluate quickly and give correct results because all the data will properly arrange in cells so that the system can take a logical path to fetch and evaluate data values. <\/span><\/span><\/span><\/p>\n

Also, by having a well-structured data model, the system\u2019s memory also consume economically avoiding occupying memory storage with access data.\u00a0<\/span><\/span><\/span><\/p>\n

Best practice for data modeling in QlikView is all about making your data well structured and logically feasible to optimize data processing and analysis in QlikView. <\/span><\/span><\/span><\/p>\n

This can achieve by plotting out a design with specific operations (ETL) you need to perform on your intended data set in order to get your data in a perfect data model.<\/span><\/span><\/span><\/p>\n

Best Practice for Data Modeling in QlikView<\/h3>\n

In QlikView, it prefers that you must design your data loading so that the data (in tables) takes the form of a star schema in QlikView<\/strong>. In a star schema, ideally, there is a fact table at the center containing the key fields that servers as a link to other tables. <\/span><\/span><\/span><\/p>\n

The fact table also contains the numbers or measure values for calculation. Branching from this central fact table are the dimension tables which link to the central table by corresponding key fields. <\/span><\/span><\/span><\/p>\n

In QlikView, the process of data loading can also explain by the process of ETL i.e. Extract, Transform and Load which encompasses all the operations and processes perform with data from start to end. Let us understand this process in some detail,<\/span><\/span><\/span><\/p>\n