Results 1 to 2 of 2

Thread: sp timeout

  1. #1
    Join Date
    Feb 2004
    Bangalore, India

    Unanswered: sp timeout

    i have an sp, which usually gives results within 30s.. (the time displayed in SQL QA). at times, the application gives a timeout error after calling this sp.
    when i chekc the app logs, it says odbc timeout expired.

    i ran profiler and invoked the sp thru the app and noticed that there is no sp: completed event for the particular sp call.

    wen i execute the sp with same parameters in SQL QA, its returning results, without a timeout error.

    please let me know what all events shall i monitor in SQL profiler?
    in general, what could be the possible reasons for such a behaviour?

    Note: this behaviour is not consistent, sometimes the app shows timeout error and sometimes its working fine.


  2. #2
    Join Date
    Nov 2004
    on the wrong server
    Provided Answers: 6
    you should not have 30 second queries in your app, but this sounds like to me it is the default command timeout for ADO.Net which is 30 seconds. If you do not specify a command timeout it will use this default. Specify a higher timeout for your command object or fix your query\design.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts