Hi,
My broker service is configured to use a particular stored proc as the
Activation procedure. It basically inserts some data into a table, then
runs sp_start_job to fire off a sql job (this all takes place on a single
SQL Server). When the queue receives its message, the procedure runs great.
However the sp_start_job is not running the job, yet there is no indication
of any error. The job simply doesn't run.. If I manually run the code in
the proc, the job fires off, so I'm fairly certain the code is syntactically
correct. Would there be any security concerns that I should obvserve when
having the activation stored proc run something like sp_start_job? anything
else that would prevent the job from starting up?
thanks.
Roger Wolter[MSFT] - 13 Nov 2006 06:19 GMT
Check the SQL Server error.log file for errors. Chances are the user that
the activated sp is running under does have permissions to start a job.
Remus has quite a bit of information on running tasks from an activated
procedure and the security implications involved in his blog:
http://blogs.msdn.com/remusrusanu/

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
> Hi,
>
[quoted text clipped - 10 lines]
>
> thanks.