Deploying Package with Child Packages

  • I'm new to deploying SSIS packages and I need to know how I should set the file string for the child packages when I deploy the packages? For example, in BIDS when I setup the connection for a child package I browse to C:\Developement\SSIS\Packages\PackageName, but when I deploy the package to my SSIS server I'll be deploying to another location on the server.

  • Jack,

    That is particularly tricky.. If you have an exec package for each I might suggest using a package configuration that easily allows you to repoint the exec component. If I have a number of packages to execute I often read the list from a table and execute them within a foreach loop. The table includes the full path to the files. I usually like to store them in the server instead of the file system because I then know they got backed up..

    CEWII

  • Elliot,

    Thanks. The situation is a fairly complex ETL (to me) where I have broken out pieced in the flow into separate packages for manageability and I probably should have done more of that. I like the idea of having a master package that executes all the others, but I wasn't sure how to make that work once deployed. I could look this up, but I'll ask here, what is the connection string for a package stored in MSDB?

  • Another option is to point to the child packages location in the SSIS server folder (if you deployed them to the MSDB database).

    If you have the same folder structure set-up in the Test server and Production, you can deploy between them without the need to change anything.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Jack,

    I can help you with that. I have attached a package that does what you are talking about. There is other stuff there but you get the point. This comes from an auditing solution I have been working on for CodePlex. I hope to have it up in a couple months.

    Koen,

    Absolutely use directories in SSIS. By policy if you deploy to the root of the msdb packages it is assumed they were deployed wrong and deleted by me. I require directory use in SSIS. I didn't like the way DTS did it with the long list and no idea what goes together.

    CEWII

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply