2 Pointer to BradC's answer
source | link

The parameters you provide aren't something you "use" in the package; they change the starting value of the property you're trying to update.

Some properties may really not let you directly set them directly. If that appears to be the problem, then see if you can set the property to an expression within the package itself. If so, make that expression an SSIS variable, and set the value of that variable when you run the package.

(Note that, if you've got a large number of items to configure, and you can't use a database, a configuration XML file (as suggested by BradC) would be easier to manage than trying to set dozens of values on the command line or in a SQL job.)

The parameters you provide aren't something you "use" in the package; they change the starting value of the property you're trying to update.

Some properties may really not let you directly set them directly. If that appears to be the problem, then see if you can set the property to an expression within the package itself. If so, make that expression an SSIS variable, and set the value of that variable when you run the package.

The parameters you provide aren't something you "use" in the package; they change the starting value of the property you're trying to update.

Some properties may really not let you directly set them directly. If that appears to be the problem, then see if you can set the property to an expression within the package itself. If so, make that expression an SSIS variable, and set the value of that variable when you run the package.

(Note that, if you've got a large number of items to configure, and you can't use a database, a configuration XML file (as suggested by BradC) would be easier to manage than trying to set dozens of values on the command line or in a SQL job.)

1
source | link

The parameters you provide aren't something you "use" in the package; they change the starting value of the property you're trying to update.

Some properties may really not let you directly set them directly. If that appears to be the problem, then see if you can set the property to an expression within the package itself. If so, make that expression an SSIS variable, and set the value of that variable when you run the package.