Question: In building a large point-of-sale data warehouse, where retailers are constantly bought and sold, and/or they consistently sent bad data, is there anything I can do in the design to account for the fact that I will always have to back out, reload, recast and rebuild aggregates on a regular basis? I'm almost to the point of scraping a data warehouse design (which is defined as non-volatile) and going with more of an ODS design (volatile, updateable, yet queryable). Any thoughts or experiences in this area?

Chuck Kelley's Answer: Sounds right to me. Then after the data is "fixed," I would move it to the data warehouse.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access