EDWH
EDWH
and current data. The schema used to store transactional databases is the entity
model (usually 3NF).[2]
Predictive analysis
Predictive analysis is about finding and quantifying hidden patterns in the data
using complex mathematical models that can be used to predict future outcomes.
Predictive analysis is different from OLAP in that OLAP focuses on historical da
ta analysis and is reactive in nature, while predictive analysis focuses on the
future. These systems are also used for CRM (Customer Relationship Management).[
3]
Software tools[edit]
The typical extract-transform-load (ETL)-based data warehouse uses staging, data
integration, and access layers to house its key functions. The staging layer or
staging database stores raw data extracted from each of the disparate source da
ta systems. The integration layer integrates the disparate data sets by transfor
ming the data from the staging layer often storing this transformed data in an o
perational data store (ODS) database. The integrated data are then moved to yet
another database, often called the data warehouse database, where the data is ar
ranged into hierarchical groups often called dimensions and into facts and aggre
gate facts. The combination of facts and dimensions is sometimes called a star s
chema. The access layer helps users retrieve data.[4]
This definition of the data warehouse focuses on data storage. The main source o
f the data is cleaned, transformed, cataloged and made available for use by mana
gers and other business professionals for data mining, online analytical process
ing, market research and decision support.[5] However, the means to retrieve and
analyze data, to extract, transform and load data, and to manage the data dicti
onary are also considered essential components of a data warehousing system. Man
y references to data warehousing use this broader context. Thus, an expanded def
inition for data warehousing includes business intelligence tools, tools to extr
act, transform and load data into the repository, and tools to manage and retrie
ve metadata.
Benefits[edit]
A data warehouse maintains a copy of information from the source transaction sys
tems. This architectural complexity provides the opportunity to :
Congregate data from multiple sources into a single database so a single query e
ngine can be used to present data.
Mitigate the problem of database isolation level lock contention in transaction
processing systems caused by attempts to run large, long running, analysis queri
es in transaction processing databases.
Maintain data history, even if the source transaction systems do not.
Integrate data from multiple source systems, enabling a central view across the
enterprise. This benefit is always valuable, but particularly so when the organi
zation has grown by merger.
Improve data quality, by providing consistent codes and descriptions, flagging o
r even fixing bad data.
Present the organization's information consistently.
Provide a single common data model for all data of interest regardless of the da
ta's source.
Restructure the data so that it makes sense to the business users.
Restructure the data so that it delivers excellent query performance, even for c
omplex analytic queries, without impacting the operational systems.
Add value to operational business applications, notably customer relationship ma
nagement (CRM) systems.
Make decision support queries easier to write.
Generic data warehouse environment[edit]
The environment for data warehouses and marts includes the following:
Source systems that provide data to the warehouse or mart;
Data integration technology and processes that are needed to prepare the data fo
r use;
Different architectures for storing data in an organization's data warehouse or
data marts;
Different tools and applications for the variety of users;
Metadata, data quality, and governance processes must be in place to ensure that
the warehouse or mart meets its purposes.
In regards to source systems listed above, Rainer[clarification needed] states, A
common source for the data in data warehouses is the company s operational databa
ses, which can be relational databases .[6]
Regarding data integration, Rainer states, It is necessary to extract data from s
ource systems, transform them, and load them into a data mart or warehouse .[6]
Rainer discusses storing data in an organization s data warehouse or data marts.[6
]
Metadata are data about data. IT personnel need information about data sources; d
atabase, table, and column names; refresh schedules; and data usage measures .[6]
Today, the most successful companies are those that can respond quickly and flex
ibly to market changes and opportunities. A key to this response is the effectiv
e and efficient use of data and information by analysts and managers.[6] A data w
arehouse is a repository of historical data that are organized by subject to supp
ort decision makers in the organization.[6] Once data are stored in a data mart
or warehouse, they can be accessed.
History[edit]
The concept of data warehousing dates back to the late 1980s[7] when IBM researc
hers Barry Devlin and Paul Murphy developed the "business data warehouse". In es
sence, the data warehousing concept was intended to provide an architectural mod
el for the flow of data from operational systems to decision support environment
s. The concept attempted to address the various problems associated with this fl
ow, mainly the high costs associated with it. In the absence of a data warehousi
ng architecture, an enormous amount of redundancy was required to support multip
le decision support environments. In larger corporations it was typical for mult
iple decision support environments to operate independently. Though each environ
ment served different users, they often required much of the same stored data. T
he process of gathering, cleaning and integrating data from various sources, usu
ally from long-term existing operational systems (usually referred to as legacy
systems), was typically in part replicated for each environment. Moreover, the o
perational systems were frequently reexamined as new decision support requiremen
ts emerged. Often new requirements necessitated gathering, cleaning and integrat
ing new data from "data marts" that were tailored for ready access by users.
Key developments in early years of data warehousing were:
1960s General Mills and Dartmouth College, in a joint research project, develop
the terms dimensions and facts.[8]
1970s ACNielsen and IRI provide dimensional data marts for retail sales.[8]
1970s Bill Inmon begins to define and discuss the term: Data Warehouse.[citation
needed]
1975 Sperry Univac introduces MAPPER (MAintain, Prepare, and Produce Executive R
eports) is a database management and reporting system that includes the world's
first 4GL. First platform designed for building Information Centers (a forerunne
r of contemporary Enterprise Data Warehousing platforms)
1983 Teradata introduces a database management system specifically designed for
decision support.
1983 Sperry Corporation Martyn Richard Jones [9] defines the Sperry Information
Center approach, which while not being a true DW in the Inmon sense, did contain
Wikimedia Shop
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
???????
Az?rbaycanca
?????????
Catal
Ce tina
Dansk
Deutsch
????????
Espaol
?????
Franais
???
Hrvatski
Bahasa Indonesia
Italiano
?????
Latvie u
Lietuviu
Lumbaart
Magyar
??????
??????????
Nederlands
???
Norsk bokml
Polski
Portugus
Romna
???????
Slovencina
Svenska
?????
???
Trke
??????????
Ti?ng Vi?t
??
Edit links
This page was last modified on 19 February 2015, at 22:23.