This project is read-only.

Command Line Parameter Inconsistency


We use the SSIS Package Store for all out packages. If you click the Command Line tab in the job step and copy paste and run using DTLoggedExec, you will get paramater errors for every paramater. Why did you decide to make the command line paramaters parse differently then DTExec? I was expecting them to be parsed the same, but they are not. For example: DTExec accepts /SET "Property";"Value", but DTLoggedExec it must be /Set:"Property";"Value" otherwise you get an error. Also, why are the parameters case sensitive? On the wiki, it shows the parameters as upper case. But otherwise, great tool for troubleshooting without having to make any package changes. Awsome job!


manowar wrote Mar 16, 2009 at 3:47 PM

Hi Adam
the command line paremeters are parsed differently from DTExec because I'm using a ready-made class to parse them. It's a class done by Peter Hallam of Microsoft some times ago, that I used to avoid wasting time to write commodity code. Anyway now I just found that there is another CodePlex MS project: that looks very promising and very flexible. I'll try to update DTLoggedExec in order to use it to fix the problem.
I've also corrected the Wiki so that it correctly reflect the fact that paramteres are case-sensitive.
Thanks for the feedback!

wrote Jun 10, 2010 at 1:38 AM

Germo wrote Nov 7, 2010 at 2:52 PM

is there any progress in extending the code to use the same parameters as in dtexec?

wrote Nov 8, 2010 at 1:03 PM

manowar wrote Nov 8, 2010 at 5:34 PM

Not really. Do you need some parameter in particular that DTExec has and that is missing in DTLoggedExec?

wrote Feb 14, 2013 at 3:35 AM