从Service Broker调用时，存储过程失败，但从SSMS运行

Question

We are using Service Broker in SQL Server 2008R2 as a simple job scheduler. We send a message to the broker and it sets it to process on the requested date/time.

We have a job (stored procedure) that gets automatically scheduled by user actions in a Sharepoint site, and it's been running just fine for about a year. This stored procedure creates 2 tables if they don't exist, truncates them if they do exist, then calls 2 other stored procedures (in series) to populate each of the tables.

A few weeks ago, the 2nd of the two stored procedures started failing when the main proc "job" was initiated by the SB. If I go into SSMS, I can execute the "job" stored procedure and it runs to completion without issue (ie both called stored procedures execute without issue, and both tables are populated).

Our company, in its infinite wisdom, decided to terminate the guy who set up the Service Broker and wrote these stored procedures. I understand the stored procedures, and am beginning to get a bit of a handle on SB, but I'm at a loss as to why the 2nd stored procedure will execute from SSMS, but fails when called from the Service Broker.

The only thing I can think of is that the Service was created with this command:

CREATE SERVICE [//ScheduledJobService]
AUTHORIZATION [user ID]
ON QUEUE [dbo].[ScheduledJobQueue] ([//ScheduledJobContract])

and that something happened with his ID on the date that it stopped working. However, that doesn't account for why part of the code will execute, and how other tasks in the Service Broker are continuing to execute.

I'm at a loss for where to look and how to track this down, so any trouble shooting tips would be greatly appreciated.

Answer 1

Service broker, as a background process, needs to run things as certain users. In my broker installations I have normally created a special user for this (ie Broker_User ) with rights to whatever it needs to execute and nothing else.

If the authorizing account for that service or for the broker queue activation procedure is revoked, things will fail.

To really trace this we need to know:

• The details of the queue (create statement etc)
• The details of the activation procedure referenced above
• Information about the accounts involved

It's also possible there's code inside one of the SPs that uses EXECUTE AS which would cause an issue if the account is removed or revoked.