Scribd
Upload
27 views

Lecture 4

The document defines a data warehouse as a subject-oriented, integrated, time-variant, and nonvolatile collection of data that supports management decision making. A data warehouse consolidates data from multiple sources and stores it separately from operational databases to allow for efficient analysis. It provides a historical perspective on data over long periods of time to support decision making rather than daily operations. The architecture of a data warehouse includes extraction, transformation, and loading of data from operational sources into the warehouse for analysis and reporting.

Uploaded by

Rishi Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
27 views

Lecture 4

The document defines a data warehouse as a subject-oriented, integrated, time-variant, and nonvolatile collection of data that supports management decision making. A data warehouse consolidates data from multiple sources and stores it separately from operational databases to allow for efficient analysis. It provides a historical perspective on data over long periods of time to support decision making rather than daily operations. The architecture of a data warehouse includes extraction, transformation, and loading of data from operational sources into the warehouse for analysis and reporting.

Uploaded by

Rishi Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

What is a Data ASET

Warehouse?
• Defined in many different ways, but not rigorously.
– A decision support database that is maintained separately from
the organization’s operational database
– Support information processing by providing a solid platform of
consolidated, historical data for analysis.
• “A data warehouse is a subject-oriented, integrated, time-variant,
and nonvolatile collection of data in support of management’s
decision-making process.”—W. H. Inmon
• Data warehousing:
– The process of constructing and using data warehouses

2
Data Warehouse—Subject-Oriented ASET

• Organized around major subjects, such as customer,


product, sales
• Focusing on the modeling and analysis of data for
decision makers, not on daily operations or transaction
processing
• Provide a simple and concise view around particular
subject issues by excluding data that are not useful in the
decision support process

3
Data Warehouse—Integrated ASET

• Constructed by integrating multiple, heterogeneous data


sources
– relational databases, flat files, on-line transaction
records
• Data cleaning and data integration techniques are
applied.
– Ensure consistency in naming conventions, encoding
structures, attribute measures, etc. among different
data sources
• E.g., Hotel price: currency, tax, breakfast covered, etc.
– When data is moved to the warehouse, it is
converted.

4
Data Warehouse—Time Variant ASET

• The time horizon for the data warehouse is significantly


longer than that of operational systems
– Operational database: current value data
– Data warehouse data: provide information from a
historical perspective (e.g., past 5-10 years)
• Every key structure in the data warehouse
– Contains an element of time, explicitly or implicitly
– But the key of operational data may or may not
contain “time element”

5
Data Warehouse—Nonvolatile ASET

• A physically separate store of data transformed from the


operational environment
• Operational update of data does not occur in the data
warehouse environment
– Does not require transaction processing, recovery,
and concurrency control mechanisms
– Requires only two operations in data accessing:
• initial loading of data and access of data

6
Why a Separate Data ASET

• Warehouse?
High performance for both systems
– DBMS— tuned for OLTP: access methods, indexing, concurrency
control, recovery
– Warehouse—tuned for OLAP: complex OLAP queries,
multidimensional view, consolidation
• Different functions and different data:
– missing data: Decision support requires historical data which
operational DBs do not typically maintain
– data consolidation: DS requires consolidation (aggregation,
summarization) of data from heterogeneous sources
– data quality: different sources typically use inconsistent data
representations, codes and formats which have to be reconciled
• Note: There are more and more systems which perform OLAP
analysis directly on relational databases
7
Data Warehouse: A Multi-Tiered Architecture ASET

Monitor
Metadata & OLAP Server
Other
sources Integrator

Analysis
Operational Extract Query
DBs Transform Data Serve Reports
Load
Refresh
Warehouse Data mining

Data Marts

Data Sources Data Storage OLAP Engine Front-End Tools


8
Three Data Warehouse ASET

• Models
Enterprise warehouse
– collects all of the information about subjects spanning
the entire organization
• Data Mart
– a subset of corporate-wide data that is of value to a
specific groups of users. Its scope is confined to
specific, selected groups, such as marketing data mart
• Independent vs. dependent (directly from warehouse) data mart
• Virtual warehouse
– A set of views over operational databases
– Only some of the possible summary views may be
materialized
9
Extraction, Transformation, and Loading (ETL) ASET

• Data extraction
– get data from multiple, heterogeneous, and external
sources
• Data cleaning
– detect errors in the data and rectify them when possible
• Data transformation
– convert data from legacy or host format to warehouse
format
• Load
– sort, summarize, consolidate, compute views, check
integrity, and build indicies and partitions
• Refresh
– propagate the updates from the data sources to the
warehouse
10
Metadata Repository ASET

• Meta data is the data defining warehouse objects. It stores:


• Description of the structure of the data warehouse
– schema, view, dimensions, hierarchies, derived data defn, data
mart locations and contents
• Operational meta-data
– data lineage (history of migrated data and transformation path),
currency of data (active, archived, or purged), monitoring
information (warehouse usage statistics, error reports, audit trails)
• The algorithms used for summarization
• The mapping from operational environment to the data warehouse
• Data related to system performance
– warehouse schema, view and derived data definitions
• Business data
– business terms and definitions, ownership of data, charging
policies 11
• OLAP (Online analytical processing) definitions - Difference between
OLAP and OLTP

You might also like