In this chapter, you will learn about Dr. Codd's OLAP rules created by his own, which, according to him, a database must obey to be regarded as a real relational database.
Codd's Rules for OLAP Tools
In 1993, Dr. E.F. Codd originated twelve rules as the basis for selecting OLAP tools. The publication of these rules was the result of research carried out on behalf of Arbor Software and has resulted in a formalized redefinition of the requirements for OLAP tools. These rules are:
- Multi-dimensional conceptual view of the database
- Concept of transparency
- Concept of accessibility
- Consistent reporting performance
- Client-server architecture
- Generic dimensionality
- Dynamic sparse matrix handling
- Multi-user support
- Unrestricted cross-dimensional operations
- Intuitive data manipulation
- Flexible reporting
- Unlimited dimensions and aggregation levels
Let us discuss all of these rules in brief:
- Multi-dimensional conceptual view: OLAP tools should allow users with a multi-dimensional model that keeps up a correspondence to users' views of the enterprise and is intuitively analytical and straightforward to use. Interestingly, this rule is given various levels of support by sellers who disagree that a multi-dimensional conceptual view of data can be delivered without multi-dimensional storage.
- Transparency: The OLAP technology has the underlying database and architecture, and the likely heterogeneity of input data sources that should be apparent to users. This necessity is to preserve the user's productivity and proficiency with familiar front-end environments and tools.
- Accessibility: The OLAP tool also lets to access data needed for the analysis from all heterogeneous enterprise data sources such as relational, non-relational, and legacy methods.
- Consistent reporting performance: With the number of dimensions, levels of aggregations, and the size of the database raises, users ought not to perceive any significant fall in performance. There should be no change in the way the key figures are calculated, and the system models must have to be strong enough to cope with changes to the enterprise model.
- Client-server architecture: The OLAP system should be proficient enough to operate efficiently in a client-server environment. The architecture should permit optimal performance, flexibility, adaptability, scalability, and interoperability.
- Generic dimensionality: Every data dimension must be the same in both structure and operational capabilities, i.e., the basic structure, formulae, and reporting should not be biased towards any one dimension.
- Dynamic sparse matrix handling: The OLAP system should be able to cope up with the physical schema to the specific analytical model that optimizes sparse matrix handling to achieve and maintain the required level of performance.
- Multi-user support: The OLAP system should be able to hold up a group of users working at the same time on the same or different models of the enterprise's data.
- Unrestricted cross-dimensional operations: The OLAP system must be able to identify the dimensional hierarchies and automatically perform associated roll-up calculations across dimensions.
- Intuitive data manipulation: Slicing and cubing, consolidation (roll-up), and other manipulations can be accomplished via direct 'point-and-click' or 'drag-and-drop' actions on the cells of the cube.
- Flexible reporting: The capability of arranging rows, columns, and cells in a way that facilitates analysis by an intuitive visual presentation of analytical reports must exist.
- Unlimited dimensions and aggregation levels: Depending on business needs, an analytical model may have some dimensions, each having multiple hierarchies.
Here are few other related articles for you to read: