This feature lets you quickly deploy SSIS packages directly from SSDT 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.
BI Developer Extensions adds a custom tab to the screen that pops up. Flip to the “Deploy (BI Developer Extensions)” tab and edit the properties to specify how you want to deploy your solution.
The following types of deployment mechanisms are supported:
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). BI Developer Extensions allows you to save separate deployment destination settings per Visual Studio configuration.
When you click the OK button, your BI Developer Extensions settings for Deploying SSIS Packages are saved into a file in the project directory called
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:
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.