Upgrading to the latest ZappySys SSIS PowerPack is a straightforward process, and when done correctly, it ensures your existing SSIS packages continue to run without disruption. The SSIS PowerPack is designed with backward compatibility in mind, so older packages built on previous versions remain fully functional after the upgrade. This article outlines the recommended upgrade strategy and the exact steps you should follow to perform a safe, controlled update on both development and production environments.
Will Older SSIS Packages Break After SSIS PowerPack Upgrade?
No — your older packages will continue to work.
Short Summary
- ZappySys SSIS PowerPack is backward-compatible.
- Your existing SSIS packages will load the updated components automatically.
- No rebuild or redeploy is needed.
- All connection managers and settings remain untouched.
Bottom line:
You can upgrade without breaking existing packages.
Recommended Upgrade Strategy
To upgrade ZappySys SSIS PowerPack on a production SQL Server with continuously running SSIS packages, follow these best-practice guidelines:
1. Identify All Environments Using SSIS PowerPack
- Check which servers (DEV / QA / PROD) have ZappySys SSIS PowerPack installed.
- Identify which SSIS packages rely on ZappySys components (REST, JSON, XML, OAuth, etc.).
2. Steps you need to follow to update the SSIS PowerPack:
- Download the latest SSIS PowerPack installer on the machine.
- Stop all SQL Server Agent jobs that use ZappySys components on the server, and close Visual Studio and SQL Server instances on both server and development machines.
- Uninstall the existing ZappySys SSIS PowerPack from Control Panel
(Control Panel → Add/Remove Programs → Uninstall SSIS PowerPack). - Install the newly downloaded version using Typical / Default settings.
- Start all previously stopped jobs and test them.
- No rebuild is required for older SSIS packages—everything will continue to run normally.
3. Test Upgrade in a Lower Environment First (Mandatory)
This is the most critical step to avoid production breakage.
Perform upgrade in DEV/QA:
- Install the latest SSIS PowerPack.
- Test all jobs:
- Connection managers
- OAuth tokens / API calls
- JSON/REST/XML transformations
Recommended:
Proceed to PROD once you confirm success in QA.
4. Schedule Production Upgrade During Planned Maintenance
Because SSIS PowerPack installs system DLLs and SSIS components, it requires:
- Restart of SSIS service (SSISScaleOutMaster, SSISScaleOutWorker if used)
- Jobs using SSIS PowerPack must not be running
Recommended:
Plan a 15-30 minute maintenance window.
5. Restart SQL Server Agent / SSIS Services (optional)
This ensures all components pick up the latest binaries.
6. Validate Critical Jobs After Upgrade
- Manually trigger 1–2 critical SSIS packages.
- Review logs for:
- Assembly version conflicts
- API connectivity
- JSON/REST parsing
7. Rollback Plan (If Anything Fails)
ZappySys installer allows:
- Reinstallation of the previous version (you should keep a backup installer).
- No need to reconfigure connections.
Rollback takes 5–10 minutes if needed.
Summary
By testing in QA, planning a short maintenance window, using in-place upgrade, and restarting services, you can safely upgrade without impacting continuously running packages.