This is an oldie but a goodie, maybe there's a trick I haven't heard about?
When I create an OperatingSystem (CmdExec) job step, it seems to only execute the first line command.
So if the first line is:
It executes dtexec. Fine.
But if I have two command lines:
It only executes the set command and never calls dtexec. Bummer.
Now, we can work around this by executing a .cmd file, but then I have a whole issue of deploying .cmd files in different environments yada yada.
So the question is, is there any (new-ish) magic trick that will tell the SQL Agent job step to execute two or more command lines right from the job?
View Complete Post