I have an SSIS package on a testing server (NPKSTADAT01) that expects a parameter (e.g. UserID). Since the SSIS Package wants a specific UserID value, we have - to this point - created several SQL Agent Jobs on STAGE that run the package, passing in a '/set "\Package.Variables[User::UserID].Value"' parameter and this works just fine. However, using this scheme will force us to create more and more jobs as we get more and more UserIDs... which is not desirable.
I thought about using DTEXEC to run the package and have a BAT (or a Windows Script) file prompt the user for the UserID to run against. Since we're not opening a CMD window directly on the server, I presume that we have to pass in the "/Server NPKSTADAT01" on the DTEXEC command line. I further assumed that we could specify the DTSX package to run via the /File parameter, and we could /Set the package variables - all on one DTEXEC command string. However, DTEXEC apparently doesn't like the FILE and SERVER options used at the same time - I get the following error:
The File option cannot be specified with the DTS, SQL, Server, User, or Password options.
So - How do I run an SSIS Package on a "remote" server, passing in a value for a package variable? Is there some trick I'm not aware of?
Thanks, Patrick