3

I have deployed a package with 2 package parameters which had their values set inside the package prior to deployment. However if I look at those parameters in my SSIS catalog project the values of them are blank.

Is this usual behaviour? Shouldn't the values have been passed to the parameters in my SSIS catalog?

Thanks

Improve this question
2
  • are the parameters set to sensitive?
    – jhowe
    May 20, 2014 at 12:27
  • No they are set to required
    – Tom
    May 20, 2014 at 12:50

2 Answers 2

Reset to default
1

I would check what is setting the parameter value and make sure it is actually being set by debugging and setting a watch. Also make sure that your parameter isn't being overwritten by a blank environment variable or something when it's deployed.

Improve this answer
1
  • Well I have set a literal value to the parameter in my SSIS package and there are no environments set up.
    – Tom
    May 20, 2014 at 12:52
0

If parameter is set to required, it means that the paramter value must be entered by user when he runs the deployed package. Set required option to false, and you should be good.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.