Upgrade Advanced ETL Processor after backing up the repository database and checking the target machine requirements. The application can be reinstalled, but packages, transformations, connections, reports, SQL scripts, and execution history live in the repository. That is the part you protect first.
What You Will Learn
- Prepare the repository database before an upgrade.
- Back up project objects, packages, transformations, and settings.
- Check software requirements before installing the newer version.
- Verify repository access and existing workflows after the upgrade.
Before You Start
Do not test an upgrade first on the only production repository. Back it up, confirm where it is stored, and make sure someone can restore it before changing the installed version.
Upgrade Preparation Docs
The Repository Database documentation is the first upgrade reference to check. It explains that the repository stores user data, configuration, and project details. In practice, that means transformations, packages, connections, reports, SQL scripts, and related project work depend on the repository being available after the upgrade.
Before upgrading, review transferring data between repositories and repository object synchronization. Those sections are useful when an upgrade also involves moving work to another repository or environment.
The requirements page covers Windows support, required drivers, hardware guidance, and repository database expectations. Its repository database section notes that the repository stores critical information and should not be lost. That is polite documentation wording for "make a backup before touching anything".
If the repository schema or enabled features need attention after an upgrade, check the repository database update guides and the wrong repository version troubleshooting page.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.