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

Resource Portals
Business Intelligence
Business Performance Management
Data Integration
Data Quality
Data Warehousing Basics
EAI
EDM
EII
ETL
More Portals...

Advertisement

Information Center
DM Review Home
Conference & Expo
Web Seminars & Archives
Newsletters
Current Magazine Issue
Magazine Archives
Online Columnists
Ask the Experts
Industry News
Search DM Review

General Resources
Bookstore
Industry Events Calendar
Vendor Listings
White Paper Library
Glossary
Software Demo Lab
Monthly Product Guides
Buyer's Guide

General Resources
About Us
Press Releases
Awards
Media Kit
Reprints
Magazine Subscriptions
Editorial Calendar
Contact Us
Customer Service

Ask the Experts Question and Answer

Ask the Expert

Meet the Experts
Ask a Question (Names of individuals and companies will not be used.)
Question Archive
Ask the Experts Home

Q:  

What is the typical rate within data warehousing for promoting changes that effect transformation and data cleansing for existing subject areas that are in production? My experience is from the operational side where changes or releases to Production are carefully planned out and done on a quarterly and sometimes monthly basis.

A:  

Douglas Hackney's Answer: Just after release, there is commonly a flurry of changes and modifications as data quality and other issues are revealed by use and utilization. Shops with more process rigor and structured processes will usually settle into a bi-monthly or monthly frequency of update to the system.

David Marco's Answer: Making changes to a production data warehouse environment is very similar to that of operational systems. Program errors/bugs are typically changed ASAP as the errors arise. Data warehouse enhancements/modifications occur on a scheduled basis...monthly, quarterly, as needed, etc).

Sid Adelman's Answer: The ETL process must be controlled just like the controls you have for operational systems. Changes to the ETL process come about from changes to the source systems (which shouldn't happen that frequently), identification of data quality problems that require changes in the cleansing process and requests for new data. The latter two requirements come about more frequently than the first and so you need to be more flexible and be able to react more quickly than you would with traditional operational systems.

(Posted )


ARCHIVE OF QUESTIONS & ANSWERS FOR DATA QUALITY
BACK TO THE LIST OF CATEGORIES



Advertisement
advertisement
Site Map Terms of Use Privacy Policy
SourceMedia (c) 2005 DM Review and SourceMedia, Inc. All rights reserved.
Use, duplication, or sale of this service, or data contained herein, is strictly prohibited.