Best Practices for Updating Task Factory
When it comes to Task Factory, one of the most common questions I'm asked is, "How can I upgrade my SSIS packages with Task Factory components?" I'll walk you through each step of the upgrade process and explain why you should adhere to these best practices.
Back up all projects! This is arguably the most important step. Task Factory provides upgrade mapping only; it doesn't provide downgrade mapping. Once you have updated the version of Task Factory you’re using, the upgrade is permanent. If you run into any problems with the update, having a backup ensures you can safely revert to a previous version and then redeploy your projects to the functioning version.
Make sure you have copies of the Task Factory installer for both your current version and the version you are upgrading to. You'll want to make sure you have the current version you're using just in case you need to revert to it for some reason. You can check the Task Factory version by opening the Programs and Features in your Control Panel.
You can always access the latest version of Task Factory here, and you can reference the release notes here. If you need a copy of an older version of Task Factory, please contact the SentryOne Support team.
Now that you're prepared, let's test the new version in development before upgrading production.
Before you begin the upgrade process, you'll want to make sure that Visual Studio is closed and no packages that leverage Task Factory are currently running. (If a package is running while Task Factory is uninstalled, it will corrupt the Task Factory components because the assemblies are missing.) Then, upgrade the version of Task Factory in your development environment by following these steps. Once the update is complete, perform a test run of your packages to ensure the new version is functioning as expected!
Testing the new version in a controlled environment is essential to ensure that the upgrade won't introduce any issues. The SentryOne team performs a full battery of testing for new versions, of course, but keep in mind there are several environmental factors that might have unexpected effects. If you do encounter problems with Task Factory components during testing, you can contact the SentryOne support team for assistance.
Make sure no packages are running during the upgrade process and follow these steps to upgrade Task Factory in your production environment.
Monitor the next run of your SSIS packages to ensure no errors occur. If any packages error on the first run and the resolution isn't obvious (like an expired credential for a connection manager), revert to your last stable version of Task Factory and redeploy all projects using your backup from step 1. Your production environment can then continue to run as usual using the old version while you troubleshoot the problem in production.
By following the steps outlined in this blog post, you can ensure a smooth upgrade to the latest version of Task Factory. As always, if you need assistance with Task Factory, don’t hesitate to reach out to the SentryOne Support team for help!