Data Warehouse
Data Warehouse
Data Warehouse
Data warehouse (DW or DWH), also known as an enterprise data warehouse (EDW), is a system used
for reporting and data analysis and is considered a core component of business intelligence. Data
warehouses are central repositories of integrated data from one or more disparate sources. They store
current and historical data in one single place that are used for creating analytical reports for workers
throughout the enterprise. This is beneficial for companies as it enables them to interrogate and draw
insights from their data and make decisions.
The data stored in the warehouse is uploaded from the operational systems (such as marketing or sales). The
data may pass through an operational data store and may require data cleansing for additional operations to
ensure data quality before it is used in the data warehouse for reporting.
Historical data.
Derived data.
Metadata.
Data warehouse design takes a method different from view materialization in the industries. It
sees data warehouses as database systems with particular needs such as answering management
related queries. The target of the design becomes how the record from multiple data sources
should be extracted, transformed, and loaded (ETL) to be organized in a database as the data
warehouse.
1. "top-down" approach
2. "bottom-up" approach
Data marts include the lowest grain data and, if needed, aggregated data too. Instead of a normalized database for
the data warehouse, a denormalized dimensional database is adapted to meet the data delivery requirements of data
warehouses. Using this method, to use the set of data marts as the enterprise data warehouse, data marts should be
built with conformed dimensions in mind, defining that ordinary objects are represented the same in different data
marts. The conformed dimensions connected the data marts to form a data warehouse, which is generally called a
virtual data warehouse.
The advantage of the "bottom-up" design approach is that it has quick ROI, as developing a data mart, a data
warehouse for a single subject, takes far less time and effort than developing an enterprise-wide data warehouse.
Also, the risk of failure is even less. This method is inherently incremental. This method allows the project team to
learn and grow.
Advantages of bottom-up design
It is just developing new data marts and then integrating with other data marts.
the locations of the data warehouse and the data marts are reversed in the bottom-up approach design.
Differentiate between Top-Down Design Approach and Bottom-Up Design
Approach
Breaks the vast problem into smaller Solves the essential low-level problem and integrates them into
subproblems. a higher one.
Inherently architected- not a union of several Inherently incremental; can schedule essential data marts first.
data marts.
It may see quick results if implemented with Less risk of failure, favorable return on investment, and proof of
repetitions. techniques.