4.2 Semantic Layer – Data Model

Relational database schemas are often designed using normalized forms that are efficient for data storage. Normalization reduces redundancy and helps maintain data integrity. However, normalized designs also make it difficult for non-experts to understand the structure of the database, and require complex queries to retrieve meaningful data. This creates a barrier between business users and the data that they require to make decisions.

To remove this restriction and facilitate greater access to data, Style intelligence provides a data representation called a data model. The data model allows you to expose business data to report designers and end users in a way that is easy for them to understand and use. You can create data models for any type of database.

Data models are not available for the 'Hadoop Hive' JDBC type.

A data model comprises a physical view, logical model, and optional hierarchical overlay. These components are described below:

Physical View: A physical view specifies a subset of database tables and the join relationships between them, covering all or part of the database schema. The physical view transforms the original database schema into a business intelligence-friendly schema, which can then be exposed to designers and end users through one or more logical models. See Physical View for information on constructing a physical view.

Logical Model: A logical model is based on a single physical view, and presents a business-oriented, easy-to-understand representation of the physical view by mapping database tables into entities and columns into attributes. The logical model denormalizes the data (adds additional redundancy) in order to maximize simplicity for data analysts and end users. See Logical Model for information on constructing a logical model.

Hierarchical Overlay: A hierarchical model (OLAP overlay) is a mapping that allows OLAP operations to be used on non-OLAP databases. See OLAP Overlay – Multidimensional Analysis for information on constructing a hierarchical model.

<< 4.1.4 Adding Additional Connections © 1996-2013 InetSoft Technology Corporation (v11.5) 4.3 Physical View >>