This project has moved and is read-only. For the latest updates, please go here.

Feature Request: Improved SSIS deployment

Topics: Resolved
Nov 21, 2008 at 4:15 PM
I have a feature request for consideration. We have projects containing a large number of packages (50+) all using package configuration files for defining their connection strings. Running a build with the Create Deployment Utility enabled results in Out of Memory exceptions as BIDS tries to open all the packages in the project. I assume it does this to determine the configuration files used by each package so they can be copied to the deployment directory. What would be great is an improved method of copying the package files and their related config files to the deployment directory and generating the manifest file so that BIDS does not open all the package files at once.

Nov 26, 2008 at 7:22 PM

We've completely avoided deploying any sort of package configurations with the Deploy SSIS Packages feature. This was purposeful. The BIDS Helper developers talked through package configurations and agreed that there are so many different approaches (SQL, env variable, dtsConfig) and so many different permutations to how people approach deployment, that it would be very difficult to tackle in BIDS Helper. So we avoided it entirely, at least for now.

More discussion here:

If you have thoughts on how deploying configurations should work, and if you have thoughts on the most common SSIS configuration schemes, feel free to comment and we'll consider it.