Data Warehousing

Get Started. It's Free
or sign up with your email address
Data Warehousing by Mind Map: Data Warehousing

1. Key Operational data

1.1. Current and Histtorical

1.1.1. Is Accesed Organized Result Integrated

2. Metadata

2.1. Describe

2.1.1. Structure of data

2.1.2. Meaning about data

2.2. Type

2.2.1. Syntactic metadata Data describing the syntax of data

2.2.2. Structural metadata Data describing the structure of the data

2.2.3. Semantic metadata Data describing the meaning of the data in a specific domain

2.2.4. Traditional metadata Approach Ontology Metadata registries

2.3. successful metadata-driven enterprise

2.3.1. Effectiveness,

2.3.2. Extensibility,

2.3.3. Reusability

2.3.4. Interoperability,

2.3.5. Efficiency and performance

2.3.6. Evolutiont

2.3.7. Etc

2.4. Provide context to the reported data

3. Process

3.1. Components

3.1.1. Data sources OLTP or ERP system External data providers Multiple independent operational “legacy"

3.1.2. Data extraction and transformation custom-written commercial software called ETL

3.1.3. Data loading staging area transformed and cleansed

3.1.4. Comprehensive database Support all decision analysi Summarized and detailed information

3.1.5. Metadata

3.1.6. Middleware tools Enable access to the data warehouse

4. Data

4.1. Integration

4.1.1. Permit data to be accessed

4.1.2. Accessible to an array of ETL

4.1.3. Analysis tools and the data warehousing environment

4.1.4. Technologies EAI SOA ETL EII

4.2. ETL

4.2.1. Extraction Reading data from one or more databases

4.2.2. Transformation Converting the extracted data

4.2.3. Load Putting the data into the data warehouse

4.3. Representation in DW

4.3.1. ​Dimensional modeling means to be implemented ​Star schema​ Snowflakes schema

4.4. Analysis

4.4.1. OLAP carry out day-to-day business functions

4.4.2. OLAP Support decision making Provide answers to business Management queries Variations ROLAP MOLAP HOLAP

4.5. Real-Time

4.5.1. Identify problems

4.5.2. Current state of business

4.5.3. assist on strategic and tactical decisions

5. Characteristics

5.1. Subject Oriented

5.1.1. organized detailed subject determine Product orientation update the database

5.2. Integrated

5.2.1. subject orientation

5.2.2. Data from different sources Into a Consistent format

5.3. Time Variant

5.3.1. Detect Trends Deviations Long Term Forecasting comparisons leading to decision making

5.4. Non Volitile

5.4.1. Changes New Data

5.4.2. Obsolet Data Discarded

5.5. additional characteristics

5.5.1. Web based

5.5.2. Relational/multidimensional

5.5.3. Client/serve

5.5.4. Real time

5.5.5. Include metadata

6. Types

6.1. data marts

6.1.1. Smaller

6.1.2. particular subject or department

6.1.3. Types Dependent Created directly from the data warehouse Consistent data model Providing quality data Data warehouse must be constructed firs End user view same version of the data that is accessed by all other data warehouse users Independent Designed for Source is not an EDW

6.2. operational data stores (ODS)

6.2.1. provides a CIF Interim staging area for a DW Updated throughout the course of business operations

6.2.2. short-term decisions Mission-critical applications

6.2.3. Consolidates data from multiple source

6.2.4. Provides a near–real-time

6.2.5. Integrated view of volatile

6.2.6. Current data

6.2.7. ETL = DW

6.2.8. Created when operational data needs to be analyzed multidimensionally

6.3. enterprise data warehouses (EDW)

6.3.1. Large-scale data warehouse

6.3.2. Integration of data

6.3.3. Provide data for many types of DSS CRM SCM BPM BAM PLM KMS Revenue management

7. Architectures

7.1. Two-Tier

7.1.1. The data warehouse

7.1.2. Data acquisition software

7.1.3. Client software

7.1.4. DSS software = DW

7.1.5. Advantages More economical Can have performance problems for large data warehouse

7.2. Three-tier

7.2.1. data and the software

7.2.2. data warehouse

7.2.3. DSS/BI/BA engine

7.2.4. advantage Separation of the functions of the data w Eliminates resource constraints It is possible to easily create data marts

7.3. Alternative

7.3.1. Independent data marts simplest and the least costly operate independently

7.3.2. Data mart bus architecture Data are linked among the individual marts

7.3.3. Hub-and-spoke architecture Attention on building a scalable and maintainable infrastructure Easy and customization of user interfaces and reports Centralized data warehouse Dependent data marts