Advanced ETL Processor version control saves versions of transformations, SQL scripts, reports, email templates, and packages. Use it before changing production ETL logic, so you can compare, recover, or revert instead of rebuilding from memory. Memory is not a backup strategy.
What You Will Learn
- Add ETL objects to version control before making risky changes.
- Save a new version with notes when a transformation, package, script, report, or email template changes.
- Use the Version Control Manager to review saved versions.
- Revert to an older version when a change needs to be backed out.
Before You Start
Add useful notes when checking in a version. Future you will not remember why the Tuesday version exists, especially if Tuesday involved CSV files.
Version Control Docs
The Version Control documentation explains how Advanced ETL Processor stores versions for transformations, SQL scripts, reports, email templates, and packages.
Start with About to understand what is versioned. The Version Control Toolbar covers managing versions, adding a version, and reverting to an old version.
Use the Version Control Manager when you need to review saved versions across objects. For larger changes, see Adding Multiple Objects so a project, group, or object can be added with notes.
Version control lives with repository-managed ETL work, so the Repository Database page is worth reviewing before moving changes between environments.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.