Portals eNewsletters Web Seminars dataWarehouse.com DM Review Magazine
DM Review | Covering Business Intelligence, Integration & Analytics
   Covering Business Intelligence, Integration & Analytics Advanced Search

View all Portals

Scheduled Events

White Paper Library
Research Papers

View Job Listings
Post a job


DM Review Home
Current Magazine Issue
Magazine Archives
Online Columnists
Ask the Experts
Industry News
Search DM Review

Buyer's Guide
Industry Events Calendar
Monthly Product Guides
Software Demo Lab
Vendor Listings

About Us
Press Releases
Advertising/Media Kit
Magazine Subscriptions
Editorial Calendar
Contact Us
Customer Service

Meta Data & Knowledge Management:
Meta Data Silos, Part 1

  Column published in DM Review Magazine
August 2003 Issue
  By David Marco

Meta data management and its use in enterprise data management have become one of the critical information technology (IT) focuses for both global 2000 corporations and large government agencies. As these entities look to reduce their IT portfolios and control escalating IT costs, they are turning to the technical functionality that a meta data repository can provide. This approach is very sound; and the organizations that have built well-architected, enterprise-wide meta data repositories have achieved a tremendous amount of success. Unfortunately, as with most popular IT trends, companies are making key mistakes in building and moving forward on their meta data management investments. One of the chief problems is that companies and agencies are not building one meta data repository; they are building several meta data repositories, none of which speak to each other and without an overall meta data management strategy. In this month's column, I will discuss this proliferation of unarchitected and disjointed meta data repositories and the problems that they cause.

The problem of disparate initiatives is not unique to meta data management. Technologies such as data warehousing, enterprise resource planning (ERP), supply chain management and all flavors of transactional systems have suffered with needless duplication and redundancy. The four most common problems with disparate meta data repositories are: missing meta data relationships, repositories built by non-meta data professionals, costly implementation and maintenance, and poor technology selections.

In past columns, I have discussed the different types of meta data (see table) that companies and government agencies need to properly manage and the importance of having these meta data objects linked.1 For example, it is very valuable for an IT developer to have the capability to look at the technical transformation rules in the meta data repository (technical meta data) that are being applied to a particular physical field name on a report that is being analyzed. Once the developer has reviewed this meta data, he/she could then navigate through the repository to find the business rules defined by the business users for that field. If a discrepancy between the transformation rules and the business rules exists, the developer could then use the meta data repository to contact the data steward that defined the specific business rules and resolve this discrepancy. This is the true power of a meta data repository: it bridges the gap between business and IT systems. When meta data is not managed from an enterprise perspective, this type of clickthrough analysis is impossible because the relationships between the meta data (both business and technical) are not being captured or maintained.

At EWS, we work with a good number of large corporations and vast government agencies. In the course of working with these groups, it is common to find many disparate meta data repository or repository-like initiatives. For example, we have one client that has more than 14 meta data repository initiatives (either in production or currently being developed) and another client that has more than 25 disjointed meta data repositories, most of which have significant monetary expenditures associated with them. Disparate meta data repository initiatives can come in many different flavors, sizes and shapes. There are large repositories that utilize enterprise-level meta data integration tools or are even custom build (typically with Microsoft SQL Server or Oracle). Also, there are lower technology meta data efforts using Microsoft Excel or Microsoft Access -- the most popular forms of meta data repository technology. Does this surprise you? Let's consider this fact for a moment. Neither Cognos nor Business Objects is the most popular form of data warehouse access. Microsoft Excel is still the most popular data warehouse access technology. This is one of the dirty secrets of data warehousing. With this in mind, it is not surprising that Microsoft Excel and Access are being improperly used for storing and retrieval of meta data.

1. For more information on this topic, see Chapter 2 in my book Building and Managing the Meta Data Repository: A Full Life-Cycle Guide (Wiley, 2000).


Check out DMReview.com's resource portals for additional related content, white papers, books and other resources.

David Marco is an internationally recognized expert in the fields of enterprise architecture, data warehousing and business intelligence and is the world's foremost authority on meta data. He is the author of Universal Meta Data Models (Wiley, 2004) and Building and Managing the Meta Data Repository: A Full Life-Cycle Guide (Wiley, 2000). Marco has taught at the University of Chicago and DePaul University, and in 2004 he was selected to the prestigious Crain's Chicago Business "Top 40 Under 40."  He is the founder and president of Enterprise Warehousing Solutions, Inc., a GSA schedule and Chicago-headquartered strategic partner and systems integrator dedicated to providing companies and large government agencies with best-in-class business intelligence solutions using data warehousing and meta data repository technologies. He may be reached at (866) EWS-1100 or via e-mail at DMarco@EWSolutions.com.

Solutions Marketplace
Provided by IndustryBrains

Data Validation Tools: FREE Trial
Protect against fraud, waste and excess marketing costs by cleaning your customer database of inaccurate, incomplete or undeliverable addresses. Add on phone check, name parsing and geo-coding as needed. FREE trial of Data Quality dev tools here.

Recover SQL Server or Exchange in minutes
FREE WHITE PAPER. Recover SQL Server, Exchange or NTFS data within minutes with TimeSpring?s continuous data protection (CDP) software. No protection gaps, no scheduling requirements, no backup related slowdowns and no backup windows to manage.

Speed Databases 2500% - World's Fastest Storage
Faster databases support more concurrent users and handle more simultaneous transactions. Register for FREE whitepaper, Increase Application Performance With Solid State Disk. Texas Memory Systems - makers of the World's Fastest Storage

Design Databases with ER/Studio: Free Trial
ER/Studio delivers next-generation data modeling. Multiple, distinct physical models based on a single logical model give you the tools you need to manage complex database environments and critical metadata in an intuitive user interface.

Free EII Buyer's Guide
Understand EII - Trends. Tech. Apps. Calculate ROI. Download Now.

Click here to advertise in this space

View Full Issue View Full Magazine Issue
E-mail This Column E-Mail This Column
Printer Friendly Version Printer-Friendly Version
Related Content Related Content
Request Reprints Request Reprints
Site Map Terms of Use Privacy Policy
SourceMedia (c) 2006 DM Review and SourceMedia, Inc. All rights reserved.
SourceMedia is an Investcorp company.
Use, duplication, or sale of this service, or data contained herein, is strictly prohibited.