• BeatleBoy - Monday, February 5, 2018 12:16 PM

    Hi,
    Basically I created my package so that I set configuration options with variables so that at runtime I can tweak the behavior of the SSIS package. For example, I have an SSIS variable that is the TargetServerName and that parameterizes a data destination. So when I deploy the package, I can change where the data gets sent by merely updating the value at runtime and not have to change the package itself. In the case of the issue I'm facing, the remote SFTP filefilter is a text string that may need to change in the future. So I was hoping to have that value set in the package runtime so that I can easily update that filter in the future without having to modify the package.

    If you're facing problem while passing values at run time, Could you go / consider with the command line prompt called DTEXEC. By opening cmd.exe you can run package and even pass values into a package variable. This functionality is pretty much same as SQL Server Agent job.

    Now, Post creation of your ssis package and provide your own parameters and try to excute as below,

    C:\Program Files\Microsoft SQL Server\100\DTS\Binn>

    DTExec.exe /f “E:\w\Integration Services Project1\Integration Services Project1\Package.dtsx†/SET \Package.Variables[User::Input_One].Properties[Value];â€29″ /SET \Package.Variables[User::Input_Two].Properties[Value];â€29″ /SET \Package.Variables[User::Name].Properties[Value];â€TestUSerâ€

    And Run the above

    Something similar we'd used previously in our test environment to implement the same.

    Could you try this approach ?