Home/ Questions/Q 6104843
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T13:53:18+00:00

I have stored procedure that insanely times out every single time it’s called from

  • 0

I have stored procedure that insanely times out every single time it’s called from the web application.

I fired up the Sql Profiler and traced the calls that time out and finally found out these things:

  1. When executed the statements from within the MS SQL Management Studio, with same arguments (in fact, I copied the procedure call from sql profile trace and ran it): It finishes in 5~6 seconds avg.
  2. But when called from web application, it takes in excess of 30 seconds (in trace) so my webpage actually times out by then.

Apart from the fact that my web application has its own user, every thing is same (same database, connection, server etc)
I also tried running the query directly in the studio with the web application’s user and it doesn’t take more than 6 sec.

How do I find out what is happening?

I am assuming it has nothing to do with the fact that we use BLL > DAL layers or Table adapters as the trace clearly shows the delay is in the actual procedure. That is all I can think of.

EDIT I found out in this link that ADO.NET sets ARITHABORT to true – which is good for most of the time but sometime this happens, and the suggested work-around is to add with recompile option to the stored proc. In my case, it’s not working but I suspect it’s something very similar to this. Anyone knows what else ADO.NET does or where I can find the spec?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve had a similar issue arise in the past, so I’m eager to see a resolution to this question. Aaron Bertrand’s comment on the OP led to Query times out when executed from web, but super-fast when executed from SSMS, and while the question is not a duplicate, the answer may very well apply to your situation.

    In essence, it sounds like SQL Server may have a corrupt cached execution plan. You’re hitting the bad plan with your web server, but SSMS lands on a different plan since there is a different setting on the ARITHABORT flag (which would otherwise have no impact on your particular query/stored proc).

    See ADO.NET calling T-SQL Stored Procedure causes a SqlTimeoutException for another example, with a more complete explanation and resolution.

    • 0