Making ETL changes

Making ETL changes

After implementation, ETL changes will fall into 1 of 5 categories:

  1. Changes to the sourcing of the existing data model where existing data in the model is unaffected
  2. Changes to the sourcing of the existing data model where existing data in the model needs to be changed
  3. Sourcing of new model fact tables/columns where historical data needs to be sourced
  4. Sourcing of new model fact tables/columns where historical data does not need to be sourced
  5. Sourcing of new dimension tables/columns

ETL changes, whether to an existing or changed data model, involve changing the ETL stored procedures for sourcing new data. The part that may be not straightforward will involve the historical data. Historical data needs to be sourced where the data is.

Any model changes that need to be made for the change must be made before the ETL changes can be made.

For any ETL changes to columns involved in reports or cubes necessitate that level of change request, change notice and testing as well. Internal review of ETL includes review of source target mapping prior to implementation. So, for changes to both ETL and the data model, the steps are:

  1. Data model changes in the modeling tool
  2. Source target Mapping
  3. Internal review of a&b
  4. Data model implementation (development environment)
  5. ETL implementation (development

    Requires Free Membership to View

    Login

    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

    By submitting your registration information to SearchCRM.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchCRM.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

  1. environment)
  2. Unit testing (development environment)
  3. Regression testing (development environment)
  4. On the implementation day, apply final changes to production
  5. Run regression tests (production environment)

For more information, check out SearchCRM's Best Web Links on Data Warehousing.


This was first published in June 2002

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

    Back to top