I would like to call an SSIS package from a Service Broker Queue.
There is one way that I am aware of -
Using xp_cmdshell from within an activation stored procedure and using DTEXEC.
Is there a more elegant way of executing an SSIS package from within SSB?
Also, I am not interested in writing a .NET external activator to process my messages in the queue. I would like this operation to be strictly database oriented. Having said this, I am also trying to avoid triggers processing the messages in the queue.
Thank you!You can schedule an SSIS package in SQL Server Agent, and then you can kick off that job via a system stored procedure.|||Not the solution I was looking for. I am aware of using sp_start_job system sp to do the job. There's gotto be a more elegant way to kick off an SSIS package from within a Service Broker Activation process.
|||
yosonu wrote:
...There's gotto be a more elegant way...
It's better than xm_cmdshell... And why must there be a more elegant way?
What do you envision as the "best" way to do this if in a perfect world?|||It hardly makes any sense for me to store SSIS packages as disabled jobs on the SQL Server Agent level.
But I do agree that this solution is still better than using xp_cmdshell for security reasons.
Thanks
sql
No comments:
Post a Comment