what is data warehouse model types

       what is data warehouse model types

Data Warehouse Models:

In this tutorial today learn data warehouse model previous tutorial provides a Three-tier data warehouse follow this link: three-tier data warehouse architecture

There are three data warehouse models

1. Enterprise:

warehouse An enterprise warehouse collect all of the information about subjects spanning the entire organization

• It provides corporate-wide data integration, usually from one or more operational systems or external

information providers, and is cross-functional in scope.

• It typically contains detailed data as well as summarized data and can range in size from few gigabytes to

hundreds of gigabytes, terabytes, or beyond. An enterprise data warehouse may be implemented on traditional mainframes, computer super servers, or parallel architecture platforms. It requires extensive business modeling and may take years to design and build

2. Data mart:

• A data mart contains a subset of corporate-wide data that is of value to a specific group of users. The scope is confined to specific selected subjects.

For example, a marketing data mart may confine its subjects to a customer, items, and sales.

The data contained in data marts tend to be summarized.

Data marts are usually implemented on low-cost departmental servers that are UNIX/LINUX or Windows-based. The implementation cycle of a data mar is more likely to be measured in weeks rather than months or years. However, it may involve complex integration in the long run if its design and planning were not enterprise-wide

• Depending on the source of data, data marts can be categorized As Codependent

or dependent. Independent data marts are sourced from data captured a frame or more operational systems or external information providers, or from data generated locally within a particular department or geographic area. Dependent date Maries are sourced directly from enterprise data warehouses

3. Virtual warehouse:

A virtual warehouse is a set of views over operational databases. For efficient query processing, only some of the possible summary views may be materialized A virtual warehouse is easy to build but requires excess capacity on operational database servers.