[Solved] How to adjust parameters of an SSIS package in SQL Server when using an SSISDB execution Script (=SP)

Question

Hello,
I created a package in Visual Studio Integration Services, where it runs successfully.
I then deployed it to SQL server 2012. Here to it runs successfully, too.
Then I changed the script in that I exchanged two variables for two parameters - doing the same thing.
I noticed that in VS no dialog window comes up where I could change the value of the parameters; here obviously I am expected to set them in Visual Studio.
However, in SQL Server 2012 the dialog window does come up when I execute the package. I can then change the value of my two parameters and the package runs OK, giving me the expected results.
Now I created a script in SQL Server from which to execute the package. Do I have to change the script every time when I want it to run with different values for the parameters?
So far I have not even found how to feed different values for the parameters into the package by using the script. Or could I tell the script somehow to bring up the dialog window for changing the parameters?
How can I set/change the package parameters by using an SSIS execution script in SQLserver?
Or how could I bring up the dialog window thru the script?
Would s.o have an example?
Help is greatly appreaciated. 
Thank you
Andreas

Answer 1

Hi,
I found out by myself and leave the answer here should s.b. else wonder about the same issue.
Look at this:
Declare
@var0 sql_variant
= 1
Exec
[SSISDB].[catalog].[set_execution_parameter_value]
@execution_id,
@object_type=30,
@parameter_name='MaxPosition',
@parameter_value=@var0
Declare
@var1 nvarchar
= 'x'
Exec
[SSISDB].[catalog].[set_execution_parameter_value]
@execution_id,
@object_type=30,
@parameter_name='NameContains',
@parameter_value=@var1
Now, what is important and was not evident to me is:
1) The variable you use for the parameters - here var0 and var1 must match in their data type the corresponding parameter used in the package.
2) The @parameter_name must match the corresponding parameter name in the package.
3) The value that is being passed to the respective package parameter is the value you specify in the Declare statement. So in my case a string x and an int 1 is used.
4) Of course the @object_type must be set to 30 for package parameters 
Then the script runs the package with adjusted parameters.
To many this might be evident, to me it was not.
Cheers
Andi
Andreas