Scribd
Upload
167 views

Chapter 3 Data Mining

The document discusses data warehousing and OLAP technology. It defines a data warehouse as a subject-oriented, integrated, time-variant and non-volatile collection of data that supports management decision making. A data warehouse involves extracting, cleaning and integrating data from multiple sources to consolidate it for analysis. It provides a historical perspective by storing data over a longer time horizon than operational systems. Data is transformed and stored separately from operational databases for efficient analytical processing without impacting transactions.

Uploaded by

bharathimanian
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
167 views

Chapter 3 Data Mining

The document discusses data warehousing and OLAP technology. It defines a data warehouse as a subject-oriented, integrated, time-variant and non-volatile collection of data that supports management decision making. A data warehouse involves extracting, cleaning and integrating data from multiple sources to consolidate it for analysis. It provides a historical perspective by storing data over a longer time horizon than operational systems. Data is transformed and stored separately from operational databases for efficient analytical processing without impacting transactions.

Uploaded by

bharathimanian
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Chapter 3: Data Warehousing and OLAP Technology: An Overview What is Data Warehouse?

Defined in many different ways. o A decision support database that is maintained separately from the organizations operational database o 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 managements decision-making process.W. H. Inmon Data warehousing:

The process of constructing and using data warehouses 1. Data WarehouseSubject-Oriented 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 2. Data WarehouseIntegrated

Constructed by integrating multiple, heterogeneous data sources o relational databases, flat files, on-line transaction records Data cleaning and data integration techniques are applied. o Ensure consistency in naming conventions, encoding structures, attribute measures, etc. among different data sources

E.g., Hotel price: currency, tax, breakfast covered, etc. o When data is moved to the warehouse, it is converted. 3. Data WarehouseTime Variant

The time horizon for the data warehouse is significantly longer than that of operational systems o Operational database: current value data o Data warehouse data: provide information from a historical perspective (e.g., past 5-10 years)

Every key structure in the data warehouse o Contains an element of time, explicitly or implicitly o But the key of operational data may or may not contain time element 4. Data WarehouseNonvolatile

A physically separate operational environment

store

of

data

transformed

from

the

Operational update of data does not occur in the data warehouse environment o Does not require transaction processing, recovery, and concurrency control mechanisms o Requires only two operations in data accessing:

initial loading of data and access of data 5. Data Warehouse vs. Heterogeneous DBMS

Traditional heterogeneous DB integration: A query driven approach o Build wrappers/mediators on top of heterogeneous databases o When a query is posed to a client site, a meta-dictionary is used to translate the query into queries appropriate for individual heterogeneous sites involved, and the results are integrated into a global answer set o Complex information filtering, compete for resources

Data warehouse: update-driven, high performance o Information from heterogeneous sources is integrated in advance and stored in warehouses for direct query and analysis 6. Data Warehouse vs. Operational DBMS

OLTP (on-line transaction processing) o Major task of traditional relational DBMS o Day-to-day operations: purchasing, inventory, banking, manufacturing, payroll, registration, accounting, etc. OLAP (on-line analytical processing) o Major task of data warehouse system o Data analysis and decision making Distinct features (OLTP vs. OLAP): o User and system orientation: customer vs. market o Data contents: current, detailed vs. historical, consolidated o Database design: ER + application vs. star + subject o View: current, local vs. evolutionary, integrated o Access patterns: update vs. read-only but complex queries

OLTP vs. OLAP 7. Why Separate Data Warehouse? High performance for both systems o DBMS tuned for OLTP: access methods, concurrency control, recovery o Warehousetuned for OLAP: complex OLAP multidimensional view, consolidation indexing, queries,

Different functions and different data: o missing data: Decision support requires historical data which operational DBs do not typically maintain o data consolidation: DS requires consolidation (aggregation, summarization) of data from heterogeneous sources o 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

You might also like