I have a ForEachLoop parent pkg that reads thru the file system of dtsx to be executed.
I would like to pass CLI parms to the command itself (dtexec). I'm not looking at passing values to the child pkgs but rather additional command line values such as:
/CONFIGFILE "C:\myconfig.dtsConfig.
In my expression builder for the PackageName I added the additional string but during the execution, the reference to my dtsconfig is ignored without any errors and the child pkg runs using the default values provided at design time.
@[User::PackageToRun] + " /CONFIGFILE C:\\myconfig.dtsConfig ".
How does one add additional CL values during the runtime for Execute Package Task
Thanks,
Anatole
How to pass command line parms to the Execute Package Task
Robert Kozak
Thanks Craig for the confirmation.
I do take advantage of Jamie's blogs and I find them very informative. Unfortunately the indirect is not as flexible as one pushes the code to other environments as to just change the dtsConfig file. The fewer instructions we have to provide to the production DBA about pushing some piece of code, the better.
I hope that for future releases, MS does consider some of the following nice to have:
1- Allow a dtsx to look into the current folder for the dtsConfig if the hardcoded path is invalid. Afterall, with SP1 we do get the warning that it is looking for the hardcoded path but eventually it goes and takes the /CONFIGFILE provided via the dtexec. So why not also have the option as the last step/resort to look into the package path when we run it via file system to check for the config file.
2- Allow command line option in the Execute Package task as mentioned above
3- Allow expressions in Execute Package task that will take the role/place of command line string or perhaps the command itself and at run time during the For Each Loop, the values can be changed accordingly as needed.
4- Add another option to the configuration dropdown that would grab/inherit the config file info from the Parent rather than just a single ParentVariable. This way at least we can set the /CONFIGFILE(s) in the parent and have the childs use it. It is not as flexible as other methods but for those child packages that use the same config file, it will work great.
5- Extend the ParentVariable in the configuration options where we could assign the path of the config file in the ParentVariable and allow the child to read it and then locate the config file and process it. Once again, this will save a lot of time trying to create individual ParentVariables if the dtsConfig has multiple settings that the child will use.
6- Need to confirm this one - If running OutOfProcess, then we should be able to specify 32bit or 64 bit dtexec. The Solution/Project flag for Run in 32 bit doesn't apply for a dtsx packages stored as file system and it defaults to that environment's dtexec call.
I'm sure there are other nice to have and I would like to see SSIS get better over time but unfortunately some of the "flexible" features that MS added to SSIS over DTS are not as flexible and forces one to go back to DOS dtexec.
Please let me know if the above will somehow make it to SSIS team for considerations or should I post them elsewhere.
Thanks again
Anatole
cmazur
sorry, executing a package with the Execute Package Task does not support the command line options that dtexec.exe does. You may want to explore the method of 'indirect configurations. Jamie wrote some notes about this and I think you will find other posts as well.
http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2342.aspx
hope this helps