11/5/12

Data mart - Wikipedia, the f ree ency clopedia

Data mart
From Wikipedia, the free encyclopedia

A data mart is the access layer of the data warehouse environment that is used to get data out to the users. The data mart is a subset of the data warehouse that is usually oriented to a specific business line or team. In some deployments, each department or business unit is considered the owner of its data mart including all the hardware, software and data.[1] This enables each department to use, manipulate and develop their data any way they see fit; without altering information inside other data marts or the data warehouse. In other deployments where conformed dimensions are used, this business unit ownership will not hold true for shared dimensions like customer, product, etc. The related term spreadmart describes the situation that occurs when one or more business analysts develop a system of linked spreadsheets to perform a business analysis, then grow it to a size and degree of complexity that makes it nearly impossible to maintain. The primary use for a data mart is business intelligence (BI) applications. BI is used to gather, store, access and analyze data. The data mart can be used by smaller businesses to utilize the data they have accumulated. A data mart can be less expensive than implementing a data warehouse, thus making it more cost effective for the small business. A data mart can also be set up in much less time than a data warehouse, being able to be set up in less than 90 days. Since most small businesses only have use for a small number of BI applications, the low cost and quick set up of the data mart makes it a suitable method for storing data.[2]

Contents
1 Design schemas 2 Reasons for creating a data mart 3 Dependent data mart 4 See also 5 References 6 Bibliography 7 External links

Design schemas
Star schema - fairly popular design choice; enables a relational database to emulate the analytical functionality of a multidimensional database Snowflake schema Data Mart Architecture Pattern (EA Reference Architecture)

Reasons for creating a data mart

en.wikipedia.org/wiki/Data_mart 1/3

11/5/12

Data mart - Wikipedia, the f ree ency clopedia

Easy access to frequently needed data Creates collective view by a group of users Improves end-user response time Ease of creation Lower cost than implementing a full data warehouse Potential users are more clearly defined than in a full data warehouse Contains only business essential data and is less cluttered.

Dependent data mart

According to the Inmon school of data warehousing, a dependent data mart is a logical subset (view) or a physical subset (extract) of a larger data warehouse, isolated for one of the following reasons: A need refreshment for a special data model or schema: e.g., to restructure for OLAP Performance: to offload the data mart to a separate computer for greater efficiency or to obviate the need to manage that workload on the centralized data warehouse. Security: to separate an authorized data subset selectively Expediency: to bypass the data governance and authorizations required to incorporate a new application on the Enterprise Data Warehousetest Proving Ground: to demonstrate the viability and ROI (return on investment) potential of an application prior to migrating it to the Enterprise Data Warehouse Politics: a coping strategy for IT (Information Technology) in situations where a user group has more influence than funding or is not a good citizen on the centralized data warehouse. Politics: a coping strategy for consumers of data in situations where a data warehouse team is unable to create a usable data warehouse. According to the Inmon school of data warehousing, tradeoffs inherent with data marts include limited scalability, duplication of data, data inconsistency with other silos of information, and inability to leverage enterprise sources of data. The alternative school of data warehousing is that of Ralph Kimball. In his view, a data warehouse is nothing more than the union of all the data marts. This view helps to reduce costs and provides fast development, but can create an inconsistent data warehouse, especially in large organizations. Therefore, Kimball's approach is more suitable form small-to-medium corporations.[3]

See also
Data warehouse Enterprise architecture OLAP cube

References
1. ^ Data Mart Does Not Equal Data Warehouse (http://www.informationmanagement.com/infodirect/19991120/1675-1.html) 2. ^ Case, Ruby (2012). Introduction to Information Systems. New Jersey: John Wiley & Sons, Inc. pp. 128.
2/3

11/5/12

Data mart - Wikipedia, the f ree ency clopedia

ISBN 978-1-118-45213-4. 3. ^ Paulraj Ponniah. Data Warehousing Fundamentals for IT Professionals. Wiley, 2010, pp. 2932. ISBN 0470462078.

Bibliography
Inmon, William (2000-07-18). "Data Mart Does Not Equal Data Warehouse" (http://csis.bitspilani.ac.in/faculty/goel/Data%20Warehousing/Articles/Data%20Marts/dataWarehouse_com%20%20Articl e_DM%20VS%20DW.htm) . DMReview.com. http://csis.bitspilani.ac.in/faculty/goel/Data%20Warehousing/Articles/Data%20Marts/dataWarehouse_com%20%20Articl e_DM%20VS%20DW.htm.

External links
Retrieved from "http://en.wikipedia.org/w/index.php?title=Data_mart&oldid=519066145" Categories: Database management systems Data warehousing This page was last modified on 21 October 2012 at 19:11. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of Use for details. Wikipedia is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.

en.wikipedia.org/wiki/Data_mart

3/3