Feeds:
Posts
Comments

Archive for July, 2013

Thanks to Devin Knight for sharing this. 🙂
Using a Deployment Manifest in SSIS allows you to deploy a set of packages to a target location using a wizard for installing your packages.  The benefit to using it is the nice user interface that a wizard provides.  The disadvantage of using it is it’s lack of flexibility.  When using the Deployment Manifest keep in mind that it’s an all or nothing deployment, which means you cannot choose to just deploy one or two packages at a time from your SSIS project.  Using the Deployment Manifest will deploy all your packages that are in your project.  Creating the manifest file is a very simple process that I will walk you through.
For more information about Managing and Configuring SSIS package download this whitepaper I co-authored on the topic.  http://www.pragmaticworks.com/downloads/ssiswhitepaper/downloadwhitepaper.aspx
Creating a Deployment Manifest
 
  • With the Solution Explorer open Right-Click on the project name and click Properties
  • This will open the Project Properties Pages
 
  • Select the Deployment Utility from the page
  • Change the CreateDeploymentUtility property to True
After you’ve gone through these steps the next time you build your project it will create the file (YourProjectName).SSISDeploymentManifest.  This file is located in the same folder as your packages in the bin\Deployment folder.
If you run this file it will open the Package Installation Wizard that will allow you to deploy all your packages that were located in the project to a desired location.
Advertisements

Read Full Post »

I have a main SSIS package that calls three other packages sequentially using the Execute Package Task control flow. Each of this Execute Package Task control was configured to obtain the location of the package from a file system. When this is included in the SSIS Deployment Manifest (Installer), it threw an error indicating the incorrect file location of the package.

To resolve this issue, each of the Execute Package Task location needs to come from SQL Server (SSIS Store) as shown in the screenshot below. Even though it says SQL Server, it is in fact pointing you to the SSIS store.

Capture

Read Full Post »

%d bloggers like this: