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.
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.
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
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access