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:

My question relates to hardware configuration for DW environments. We have a two terabyte DW that is in need of improved data integrity. One of the data issues is that DW warehouse changes to correct legacy-sourced data need to occur to the production DW because neither a quality or full model of the DW exists ? it?s a cost issue. My question is what is "recommended" related to the hardware configuration for a "typical" production environment. In the client/server development arena, I am used to the classical Production, Quality, Development environments with versioning etc. However, since we are "fixing" so many data integrity issues getting the data correct in "one" environment [i.e., production] is challenge enough.

What is typical? Are there research sources you can point me to?

A:

Clay Rehm?s Answer: There is no typical configuration. I have seen data warehouse environments match operational environments and have seen everything in between. What works for another company may or may not work for you.

You should have a development region for your unit and system testing of the ETL procedures. As soon as specific ETL procedures have passed your system tests, move the associated data and ETL into Acceptance for your end users to test and validate. However, due to other pressures, you may wish to have two regions for now ? a development/quality region and a production region until you can get a handle on your data quality issues.

There will be dirty data in your production data warehouse. However there should not be dirty ETL processes in the data warehouse. Additionally, you must create a valid data model of your data warehouse. I am not sure how you can support this warehouse without it. Exactly what kind of cost would be incurred to get a decent model of your data warehouse?

(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.