Deploy SSIS Packages

This feature lets you quickly deploy SSIS packages directly from BIDS without having to create a deployment manifest and use the Package Installation Wizard.

First, right click on the project node in Solution Explorer and choose Properties.

DeployPackagesMenus.png

BIDS Helper adds a custom tab to the screen that pops up. Flip to the "Deploy (BIDS Helper)" tab and edit the properties to specify how you want to deploy your solution.

DeployPackagesConfigurations.png

The following types of deployment mechanisms are supported:
  • Simple File Copy - Copies packages to any windows directory.
  • SQL Server Destination - Copies packages into MSDB in the specified SQL Server instance.
  • SSIS Package Store (File System) - Copies packages into the SSIS Package Store on the file system of the specified server. (The files end up in "C:\Program Files\Microsoft SQL Server\90\DTS\Packages" by default.)
  • SSIS Package Store (MSDB) - Copies packages into the SSIS Package Store in MSDB on the specified server.

It is recommended that you click the Configuration Manager button in this dialog and create one Visual Studio configuration per deploy destination (i.e. Development, Staging, Production). BIDS Helper allows you to save separate deployment destination settings per Visual Studio configuration.

When you click the OK button, your BIDS Helper settings for Deploying SSIS Packages are saved into a file in the project directory called <ProjectName>.dtproj.bidsHelper.user.

Next, deploy packages by right clicking on the packages you wish to deploy in Solution Explorer and choosing Deploy. You may right click on a single package, you may Ctrl-click multiple packages then right click on them, or you may right click on the project node to deploy all packages in the project. If you have multiple projects in the solution, all of which are SSIS projects, you can right click on the solution node and deploy all packages from all projects using that menu option.

The Output window displays details about the progress of your deployment:

DeployPackagesOutput.png

If deploying an entire project (via the project node menu or the solution node menu), a file is created in the OutputPath (usually the bin directory) called bidsHelperDeployPackages.bat which contains all the commands which were just used to deploy the packages. This bat file can be used as a starter for automating deployment.

Limitations:
  • SSIS Package Configurations are not deployed. No dtsConfig files can be deployed using BIDS Helper. BIDS Helper will not alter your packages or modify your package configurations. Package configurations should be manually setup on the destination environment before deploying your packages.
  • Only Windows Integrated Security is supported for deploying packages to SQL Server or the SSIS Package Store.
  • Packages encrypted with a password are not supported with the Deploy Packages feature unless you set DeploymentType=FilePathDestination (which is just a simple file copy that does not use dtutil and thus does not need to decrypt the package).
  • If you have customized your MsDtsSrvr.ini.xml, BIDS Helper does not account for this when deploying packages. Please follow and vote for issues SSIS Package Database Name and SSIS 2005 File System package store deployment if this impacts you.
  • This feature is not available in SSIS2012 when your project is in "project deployment model", only when it is in legacy "package deployment model". To deploy your project in project deployment model, use the built-in SSIS2012 deployment feature.

Last edited Dec 3, 2012 at 6:08 PM by furmangg, version 8

Comments

SNTKAVIN Apr 12, 2013 at 4:30 PM 
I see lots of useful functions which I was looking from SSIS. Thanks a lot.

But I do not understand the difference between "SQL Server Destination" and "SSIS Package Store (MSDB) ". I tried to find out but I couldn't .

Please explain.
Thanks