Content deleted Content added
Rework lede to something that can independently cired and moving complex detail to its own section so it can be worked on |
→Description: Section needs a rework beyond this ... |
||
Line 6:
==Description==
Dimensional modeling always uses the concepts of facts (measures), and dimensions (context). Facts are typically (but not always) numeric values that can be aggregated, and dimensions are groups of hierarchies and descriptors that define the facts. For example, sales amount is a fact; timestamp, product, register#, store#, etc. are elements of dimensions. Dimensional models are built by business process area, e.g. store sales, inventory, claims, etc. Because the different business process areas share some but not all dimensions, efficiency in design, operation, and consistency, is achieved using [[Dimension (data warehouse)#Types|conformed dimensions]], i.e. using one copy of the shared dimension across subject areas.{{cn}}▼
Dimensional modeling does not necessarily involve a relational database. The same modeling approach, at the logical level, can be used for any physical form, such as multidimensional database or even flat files. It is oriented around understandability and performance. According to him, although transaction-oriented ER is very useful for the [[Transaction processing|transaction capture]], it should be avoided for end-user delivery.▼
▲Dimensional modeling does not necessarily involve a relational database. The same modeling approach, at the logical level, can be used for any physical form, such as multidimensional database or even flat files. It is oriented around understandability and performance.
▲Dimensional modeling always uses the concepts of facts (measures), and dimensions (context). Facts are typically (but not always) numeric values that can be aggregated, and dimensions are groups of hierarchies and descriptors that define the facts. For example, sales amount is a fact; timestamp, product, register#, store#, etc. are elements of dimensions. Dimensional models are built by business process area, e.g. store sales, inventory, claims, etc. Because the different business process areas share some but not all dimensions, efficiency in design, operation, and consistency, is achieved using [[Dimension (data warehouse)#Types|conformed dimensions]], i.e. using one copy of the shared dimension across subject areas.
==Design method==
| |||