Kayal-717623 (10/31/2012)
Hi all,I have a master package to execute 200 child packages. The master package goes thru a loop and executes 5 -6 packages at a time. The configuration for these packages are stored in file system. The location of the file system is changing and due to that i need to modify the 200 packages to change the config file location. Any better ideas to prevent modifying 200 packages to use the new config file location.
Also, this master package is called in a job. Master package uses a different config file from that of the child packages.
It sounds like your .dtsConfig locations are hardcoded within your SSIS packages. So I think you're going to have touch each package to update them. I like the ideas that Andy Leonard uses in his example SSIS framework: http://sqlblog.com/blogs/andy_leonard/archive/2011/09/16/designing-an-ssis-framework.aspx
Andy's framework uses an Environment variable to point to the location for the parent .dtsConfig file. This then points to a SSIS configuration database that that contains your child package information. It's a pretty slick setup and I've probably not described it well enough. Search through Andy's blog for more posts about it.
HTH,
Rob