Execution Timeout Expired Error while executing an SQL query

• frederico_fonseca

  SSCoach

  Points: 16225

  More actions

  February 6, 2025 at 10:54 am

  #4531139

  bump for visibility.

  and speed differences may be to do with settings on ssms vs vb.net

• Jeffrey Williams

  SSC Guru

  Points: 90348

  More actions

  February 6, 2025 at 10:16 pm

  #4531619

  I would check the connection settings - and verify ARITHABORT setting is the same for both.  It definitely sounds like a different plan is being used when called from VB.NET vs SSMS and the ANSI settings can cause different plans to be generated.

  Jeffrey Williams
  “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

  ― Charles R. Swindoll

  How to post questions to get better answers faster
  Managing Transaction Logs

• Lisa Slater Nicholls

  Hall of Fame

  Points: 3461

  More actions

  February 14, 2025 at 6:22 pm

  #4537905

  how it is executed

  This might be key... is this query executed many more times than others you might be comparing it too?  If so, could the problem be an inability to get a connection from the pool?  Just a guess.

  This happened to me once in a .Net Core app, and it turned out that the query was being invoked many times as a page rendered, as certain conditions were evaluated and built up, where it should have been delayed until other stuff was set up and then invoked once.

  The actual query contents were mundane/innocuous/not relevant to the problem...