Data Warehouse
Architecture
Data Warehouse Architecture
➢A data warehouse architecture is a method of defining the
overall architecture of data communication processing and
presentation that exist for end-clients computing within the
enterprise.
➢Each data warehouse is different, but all are characterized by
standard vital components.
Common Architectures
❖Data Warehouse Architecture: Basic
❖Data Warehouse Architecture: With Staging Area
❖Data Warehouse Architecture: With Staging Area and Data Marts
Data Warehouse Architecture:
Basic
➢Operational System
An operational system is a method used in data warehousing to refer to a system that is used to
process the day-to-day transactions of an organization.
➢Flat Files
A Flat file system is a system of files in which transactional data is stored, and
every file in the system must have a different name.
➢ Meta Data
A set of data that defines and gives information about other data.
➢Lightly and highly summarized data
The goals of the summarized information are to speed up query performance. The
summarized record is updated continuously as new information is loaded into the
warehouse
➢End-User access Tools
The principal purpose of a data warehouse is to provide information to the
business managers for strategic decision-making. These customers interact
with the warehouse using end-client access tools.
The examples of some of the end-user access tools can be:
•Reporting and Query Tools
•Application Development Tools
•Executive Information Systems Tools
•Online Analytical Processing Tools
•Data Mining Tools
Data Warehouse Architecture:
With Staging Area
Staging area
❑A place where data is processed before entering the
warehouse.
❑A staging area simplifies data cleansing and consolidation for operational
method coming from multiple source systems, especially for enterprise data
warehouses where all relevant data of an enterprise is consolidated.
Data Warehouse Architecture:
With Staging Area and Data Marts
Data Marts
A data mart is a segment of a data warehouses that can provided information for
reporting and analysis on a section, unit, department or operation in the
company, e.g., sales, payroll, production, etc.
Properties of Data Warehouse
Architectures
Properties of Data Warehouse
Architectures
1. Separation: Analytical and transactional processing should be keep apart as
much as possible.
2. Scalability: Hardware and software architectures should be simple to
upgrade the data volume, which has to be managed and processed, and the
number of user's requirements, which have to be met, progressively increase.
3. Extensibility: The architecture should be able to perform new operations
and technologies without redesigning the whole system.
4. Security: Monitoring accesses are necessary because of the strategic data
stored in the data warehouses.
5. Administrability: Data Warehouse management should not be
complicated.
Types of Data Warehouse
Architectures
Single-Tier Architecture
Single-Tier Architecture
➢Single-Tier architecture is not periodically used in practice. Its purpose is to
minimize the amount of data stored to reach this goal; it removes data
redundancies.
➢ Data warehouse is implemented as a multidimensional view of operational
data created by specific middleware, or an intermediate processing layer.
➢The vulnerability of this architecture lies in its failure to meet the
requirement for separation between analytical and transactional processing.
Two-Tier Architecture
Two-Tier Architecture
1.Source layer: A data warehouse system uses a heterogeneous source of data. That data is
stored initially to corporate relational databases or legacy databases, or it may come from
an information system outside the corporate walls.
2.Data Staging: The data stored to the source should be extracted, cleansed to remove
inconsistencies and fill gaps, and integrated to merge heterogeneous sources into one
standard schema. The so-named Extraction, Transformation, and Loading Tools (ETL) can
combine heterogeneous schemata, extract, transform, cleanse, validate, filter, and load
source data into a data warehouse.
3.Data Warehouse layer: Information is saved to one logically centralized individual
repository: a data warehouse. The data warehouses can be directly accessed, but it can also
be used as a source for creating data marts, which partially replicate data warehouse
contents and are designed for specific enterprise departments. Meta-data repositories store
information on sources, access procedures, data staging, users, data mart schema, and so
on.
4.Analysis: In this layer, integrated data is efficiently, and flexible accessed to issue reports,
dynamically analyze information, and simulate hypothetical business scenarios. It should
feature aggregate information navigators, complex query optimizers, and customer-friendly
GUIs.
Three-Tier Architecture
.
Three-Tier Architecture
➢The three-tier architecture consists of the source layer (containing multiple
source system), the reconciled layer and the data warehouse layer (containing
both data warehouses and data marts). The reconciled layer sits between the
source data and data warehouse.
➢Reconciled layer is also directly used to accomplish better some operational
tasks, such as producing daily reports that cannot be satisfactorily prepared
using the corporate applications or generating data flows to feed external
processes periodically to benefit from cleaning and integration.
Three-Tier Architecture
.
Three-Tier Architecture
1.Bottom Tier (Data Warehouse Server)
2.Middle Tier (OLAP Server)
3.Top Tier (Front end Tools)
Three-Tier Architecture
Principles of Data Warehousing
