August 12, 2013 at 12:05 am
Our outsourcing partner is trying to setup a way to start SSIS jobs from BMC Control-M. There seams to be a problem doing that because the SSIS job returns control before the SSIS job has finnished. Is there a way to work around that problem?
Control-M is a central scheduler, its installed on the SQL Server batch server so Connection between Control-M and the server is no problem.
August 13, 2013 at 9:28 am
peterswe (8/12/2013)
Our outsourcing partner is trying to setup a way to start SSIS jobs from BMC Control-M. There seams to be a problem doing that because the SSIS job returns control before the SSIS job has finnished. Is there a way to work around that problem?Control-M is a central scheduler, its installed on the SQL Server batch server so Connection between Control-M and the server is no problem.
I think we'll need more details to help you solve your problem.
How is BMC Control-M starting the SSIS job from Control-M? Starting a SQL Agent job that executes the package? Using DTEXEC.EXE from a command line interface? Some other method layered on top of one of these (e.g., executing a batch file, PowerShell script, or sqlcmd that does one of these two things)?
All the ways I know to execute an SSIS package return control to the calling application with a "success" status as soon as they successfully start the job on the SSIS server. I assume that's a problem because you want to start some other process only after the SSIS package has finished running. If that's the case, you'll probably have to try one of the following: 1) include a component at the end of SSIS package that initiates the next action (e.g., a script task that launches another application), 2) include a component at the end of the SSIS package that signals some other application that the package is finished (e.g., an MSMQ task that sends an appropriate message), 3) include a data flow task at the end of the SSIS package that writes a value indicating "execution complete" to a database or a file somewhere and somehow configure the scheduling program to poll this value periodically until it indicates "execution complete" and then launch the next step in the process.
Jason Wolfkill
August 15, 2013 at 12:11 am
Thank you, a good information about how it works. I hoped there would be some way to run it in another mood so that the SSIS would wait to return until after it is ready.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply