
In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.
SQL Server. SSIS. PowerShell. Azure.
1 wife. 1 kid. 5 dogs. 10 cats.
In the first part of the series I mentioned two methods of upgrading SSIS projects (well - packages, for now) - Application.Upgrade() and Application.SaveAndUpdateVersionToXml(). This post is about the latter.
Starting to learn something new - first step. Let’s analyse the code of SSIS package. How does it store the information about the element connections? How can I get that data as graph’s edges and nodes? Step by step - building the packages from empty one to more complex I will find how they are stored.
When you deploy SSIS project basically you have two options - right click on project name and standalone tool (let’s skip SMO and stuff). Both mean the same: IsDeploymentWizard.exe
. I was curious what happens during deployment and why mode/Silent
finishes deployment very quickly, so I started digging.