Home/ Questions/Q 3361052
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T03:06:20+00:00

I’ve written a stored procedure that takes 15 min when executed from Management Studio.

  • 0

I’ve written a stored procedure that takes 15 min when executed from Management Studio. When it’s activated from Service Broker, however, after 4 hours it hasn’t done even half of its work.

Are there known performance issues when running SPs from Service Broker? (Perhaps Service Broker runs the SP inside a transaction and Management Studio doesn’t?)

I’m using SQL Server 2005.

Update:

It appears the problem was executing a stored procedure from another stored procedure. More specifically, I have a stored procedure which receives an operation (export or delete). This SP then calls the respective SP based on the operation (one has an ETL process, the other deletes data). Forcing recompile on these SPs seems to have fixed the problem. I wonder if SQL Server should make an action plan for each sub-SP though, independent of the SP that’s calling them. In that case, no recompile would be needed.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t know about Service Broker, but for general stored procedure troubleshooting check out the suggestions given at this question. They helped me a lot to figure out some problems with my stored procedures.

    You can take a look at what the stored procedure is doing with the WhoIsActive routine, you can acquire the query plan and study if there is any difference with the query plan when executed in Management Studio, you can experiment with the OPTIMIZE FOR hint to eradicate parameter sniffing…

    (Parameter sniffing is that the query plan is generated differently when other parameters are supplied. Is Service Broker passing the same parameters to your SP as the ones you pass in Management Studio?)

    Good luck and please post your findings here if you are unsuccessful.

    • 0