Creating a Deployment Manifest in SSIS

October 18, 2011

Creating an SSIS package is only one part of the puzzle when it comes to fully automating your data migration applications.  If your company is like many organizations the person developing the SSIS package is not necessarily the person who will be deploying that package into a QA or Production environment.  The question then becomes, how to we manage handing a completed package to the appropriate people when it comes time to deploy?  There are several options for this process, and the one I’m going to focus on today is the Deployment Manifest. 

The Deployment Manifest is not a one size fits all solution to deploying your SSIS packages.  I would say that it is only useful when deploying multiple packages at one time, for example an entire data warehouse ETL solution.  Let me explain.  When you create a Deployment Manifest it is done at the project level, so all of the SSIS packages that exist in that project will be included in the manifest. That can be a problem if your project has any packages that aren’t ready for deployment, or if the packages won’t all be deployed to the same server.  However if you have a contained project, and all the packages are ready for deployment, the manifest is a great way to deploy multiple packages, and the manifest comes with a handy dandy user interface.

Lets quickly walk through the process.

  • Open you SSIS Project and in the Solution Explorer pane right click on the project name and click Properties


  • This will open the Project Properties Pages. From there select the Deployment Utility from the page


  • Change the CreateDeploymentUtility property to True and click ok.


  • Next right click again on the project name and select build from the menu.


  • To find your newly created manifest file navigate to your project folder and then inside the project folder to the bin folder and then to the deployment folder. 


  • Take the contents of the folder, or just copy the folder to a designated location for the deployment manager to pick them up, or however you plan on getting them the files.  Once there, they just need to double click on the manifest file and it launches a wizard.  They can then walk through the wizard and in the end you will have successfully deployed all the packages in that project.


As I said earlier this is not a one size fits all deployment solution, but it does have its place.  I this helps you make the right choice in your deployment options.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: