We derive data in the data warehouse that does not exist in the raw source data. For example, while raw data may contain discount amount and unit price, the discount percentage, a simple division calculation, is a value-add that we can add to our data warehouses. Calculations like this that can be derived systemically should be done systemically. Users will otherwise be loathe to calculate these and use them otherwise.
If calculations, even summarizations, are derived in the operational environment, it can save time to simply source this data into the data warehouse. But can it be trusted? You should always check the calculations of calculated data in the operational environment before sourcing it into the data warehouse.
In the cases where you decide to bring calculated data into the data warehouse, check the calculations and report on the violations. Either the components of the calculations or the calculation is incorrect.
For more information, check out SearchCRM's Best Web Links on Data Quality.
Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning editorial writers on the latest customer relationship management (CRM)and call center technology issues today. Our goal is to keep you informed on the hottest issues facing this fast-changing industry.
Hannah Smalltree, Editorial Director
This was first published in May 2002
Join the conversationComment
Share
Comments
Results
Contribute to the conversation