December 13, 2010 at 9:54 pm
If I have a DOS bat file that contains a couple of del commands (to delete all files of a file type in a sibling directory) and calls a few executables is there a way to transfer that to an SSIS package? What if the SSIS/SQL Server hosting the package is on a different server from where the bat file is and where the executables are that the Bat file calls?
I tried this with the Execute Process Task and it will let me select a bat file but it fails to run. I am logged into the BI Dev Studio as my domain user and that user has FULL CONTROL enabled for the share name on the other server wherethe bat file is so this shouldn't be a permissions issue but when I try to use the Execute process Task to call a bat file that does nothing but delete files in a diretcory I get an access error.
Kindest Regards,
Just say No to Facebook!December 15, 2010 at 6:57 am
I have a couple of situations where I need to invoke a process on another server, either directly or by kicking off an "unscheduled" Scheduled Task on another server. I use the PSExec utility to do this. See http://technet.microsoft.com/en-us/sysinternals/bb897553
I think in one case I execute it via SSIS Execute Process task. In another, I just call it in a SQL Agent job step. The difference with this utility, is that the process actually executes on the remote server.
One thing to be aware of if you go this route.... there is a license dialog that appears the first time you run psexec that requires manual intervention. Once that is answered the first time it no longer appears. This tripped me up. I had a new job that would never complete because it was waiting for the dialog to be answered.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply