 - A data mart is a repository of data gathered from operational data and other sources that is designed to serve a particular community of knowledge workers. In scope, the data may derive from an enterprise-wide database or data warehouse or be more specialized. The emphasis of a data mart is on meeting the specific demands of a particular group of knowledge users in terms of analysis, content, presentation, and ease-of-use. Users of a data mart can expect to have data presented in terms that are familiar.
In practice, the terms data mart and data warehouse each tend to imply the presence of the other in some form. However, most writers using the term seem to agree that the design of a data mart tends to start from an analysis of user needs and that a data warehouse tends to start from an analysis of what data already exists and how it can be collected in such a way that the data can later be used. A data warehouse is a central aggregation of data (which can be distributed physically); a data mart is a data repository that may derive from a data warehouse or not and that emphasizes ease of access and usability for a particular designed purpose. In general, a data warehouse tends to be a strategic but somewhat unfinished concept; a data mart tends to be tactical and aimed at meeting an immediate need.
One writer, Marc Demerest, suggests combining the ideas into a Universal Data Architecture (UDA). In practice, many products and companies offering data warehouse services also tend to offer data mart capabilities or services.
 |
Learn more about SQL Server Database Modeling and Design |
| SQL Server database design disasters: What not to do: Inspired by what he recently found in some SQL Server shops, database architect Brian Walker shares advice for improved database design – and SQL Server performance. |
| Physical data storage in SQL Server 2005 and 2008: Learn the fundamentals of data storage in SQL Server 2005 and 2008, including tables, views and data types, in this book excerpt. |
| Designing SQL Server non-clustered indexes for query optimization: Optimize SQL Server non-clustered indexes and queries by considering index fields, compound indexes and SQL Server statistics' impact on non-clustered indexes. |
  |
Creating SQL Server tables and columns: Quick tips to know: Improve performance of SQL Server tables and columns by defining data types, indexes, keys, partitions and more. Create SQL Server columns and tables with these best practices. |
| Top 10 SQL Server Tips of 2008: Get the top 10 SQL Server tips of 2008 on topics such as clustered index design, log shipping setup, date/time data conversions and many other aspects of SQL Server. |
| Tutorial: SQL Server indexing tips to improve performance: Significantly improve your SQL Server performance through this tutorial on proper indexing choices. Learn how to design high performing indexes and tune your existing SQL indexes. |
| Tutorial: Learn SQL Server basics from A-Z: If you're new to SQL Server of simply want a refresher on some fundamentals, check out this tutorial on topics from security and performance to SSIS and using native tools. |
| Supertype and subtype tables in SQL Server: Learn how to physically implement supertype and subtype tables on a SQL Server in this book excerpt. |
| SQL Server and data manipulation in T-SQL: Learn about stored procedures, parameters, triggers and other T-SQL code functions in this book excerpt. |
| CONTRIBUTORS: |
Dan Gallagher, Tim D. Nelson, and Steve Proctor |
| LAST UPDATED: |
04 Feb 2010
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
Show me everything on 
