The Business Intelligence Blog

December 29, 2009

Creating Deployment Utility for Integration Services Packages

Filed under: SSIS — Tags: , , , , — Shahfaisal @ 1:26 pm

Before deploying Integration Services packages, you will need to create a Deployment Utility by configuring the project properties in Business Intelligence Development Studio(BIDS). The deployment utility creates a folder that contains all the files that you need to deploy the packages in a project. This utility is very helpful when you don’t want to deploy the packages manually. Please note that you have to create this utility if you want to use built-in deployment tools, however, if you intend to deploy the package manually or use SQL Server Management Studio(SSMS) to import the package, then you don’t need to create this utility.

To configure the project to create deployment utility, right-click the project name and select properties as shown in the figure below.

The project properties dialog box appears as shown in the figure below.

Lets go through the configuration properties:

AllowConfigurationChanges – This property specifies whether the configurations can be changed at installation time, default value is true.

CreateDeploymentUtility – This property specifies whether or not a deployment utility is created when the project is built. If set to true, the deployment utility will be created. Default value is false which means it will not be created.
I have no idea why the default value is false, if somebody knows why, please leave a comment.

DeploymentOutputPath – This property specifies the location where the Deployment Utility will be created. Note that this path is relative to the Integration Services project.

After setting the project properties, select Build from the main menu and click Build package to create the deployment utility as shown in the figure below.

To verify whether the deployment utility has been created, navigate to the \bin\Deployment folder and look for the .SSISDeploymentManifest file.

Once the deployment utility has been created, you will need to copy the contents of the folder (\bin\Deployment) to the server where you want to deploy your packages and double-click the .SSISDeploymentManifest file to launch the Package Installation Wizard. The Package Installation Wizard will walk you through the deployment process.

Advertisements

3 Comments »

  1. The only reasons I can think of are when developing a package you are not always going to be creating a deployment package. Also you wouldn’t want to create a deployment package while debugging the package.

    An alternate way to get these packages to SQL Server is to import it into SSIS.

    Hope this helps.
    Regards,
    MIT560

    Comment by MIT560 — December 29, 2009 @ 6:21 pm

  2. Ofcourse, you have to create the deployment utility ONLY when you want to use the built-in deployment tools. For example, you wont need this utility when you intend to deploy the package manually or when you use SSMS to import the package.

    Comment by Shahfaisal Muhammed — December 29, 2009 @ 8:06 pm

  3. […] utility. For more details on how to create a deployment utility, please refer to the post Creating Deployment Utility for Integration Services Packages. Once the deployment utility has been created, you will have to copy the contents of the folder […]

    Pingback by Deploying Integration Services packages using Deployment Utility « My Blog — January 14, 2010 @ 8:04 am


RSS feed for comments on this post. TrackBack URI

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: