As I took a week's break from blogging - since this is the first week of classes after the spring break - I decided to adopt this new Q/A format for blogging for the rest of the semester. And so I begin blogging about dimensional modeling in this format
What is Dimensional Modeling?
It is a set of techniques used to build a data warehouse. Each model has a set of dimensions, which are analogous to the operational tables in the database and a fact table which is analogous to the associative entity in an ER model.
How does Dimensional Modeling differ from ER Models?
Dimensional models are quiet different from ER models in the sense that they do not necessarily involve objects from the relational database. The dimensions can be even flat files. Moreover, the fact tables in dimensional modeling are loaded at fixed intervals when the operational tables are either under maintenance or under least load due to customer transactions while the dimension tables are loaded in real time as and when a transaction takes place. Also the data in dimension tables is seldom deleted while that in dimension tables/Associative entities in the ER model may be deleted once it is regarded as obsolete under the business rules.
What are some of the properties of facts?
Facts are designed to capture interesting patterns about your business that may not be evident in your transactional tables. Facts can be typically aggregated across dimensions and provide knowledge valuable to businesses.
Is it possible to normalize/de-normalize dimensions as we do in normal transactional databases?
Normalization of dimensions is possible though it is an expensive operation and thus not done usually.
What is Dimensional Modeling?
It is a set of techniques used to build a data warehouse. Each model has a set of dimensions, which are analogous to the operational tables in the database and a fact table which is analogous to the associative entity in an ER model.
How does Dimensional Modeling differ from ER Models?
Dimensional models are quiet different from ER models in the sense that they do not necessarily involve objects from the relational database. The dimensions can be even flat files. Moreover, the fact tables in dimensional modeling are loaded at fixed intervals when the operational tables are either under maintenance or under least load due to customer transactions while the dimension tables are loaded in real time as and when a transaction takes place. Also the data in dimension tables is seldom deleted while that in dimension tables/Associative entities in the ER model may be deleted once it is regarded as obsolete under the business rules.
What are some of the properties of facts?
Facts are designed to capture interesting patterns about your business that may not be evident in your transactional tables. Facts can be typically aggregated across dimensions and provide knowledge valuable to businesses.
Is it possible to normalize/de-normalize dimensions as we do in normal transactional databases?
Normalization of dimensions is possible though it is an expensive operation and thus not done usually.

