• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 703
  • Last Modified:

SSIS Package deployment

I have developed some SSIS packages in SQL Server 2005. Mainly it consists of 1 master (parent) package and 4 child packages. The master package is using "Execute SSIS Package" tasks to execute the child packages. As I am new in SSIS development my question is regarding the "Configuration" files. Should each child package have its own config file, or there should be only one config file for parent package.

I'll appreciate if you could explain a typical setup of a parent packages with multiple child packages. Also what steps should I follow for deployment. I want to use SQL Server agent for deployment. I have created XML config files for each child package.

Appreciate your help..
  • 2
1 Solution
banjara15Author Commented:

Guys, please let me know your expert feedback so I could proceed in the right direction..

Thanks agian to all..
Use the separate config files with each Child, that is fine. However, if you could pass all of the configuration data into the Parent, then the Child packages could be configured to read a Parent value. But separate files is fine too, especially if you might run the Child packages stand alone.
I prefer to pass the child values from the Parent, and only use the Child packages as such. Do you have a more specific question that I could help with?
Good Luck
banjara15Author Commented:

Thanks a lot for your help. I decided to use only one config file for the main package. For all the child packages I am passing the value through the variable...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now