Post reply

"Microsoft ODBC SQL Server Driver Timeout expired" ??

  • October 7, 2004 at 9:02 am

    #108728

    Hello,

    There ais a view that runs an intense SELECT query. When using Enterprise Manager (MSSQL 2000) the results do no display, and after about 60 sec the following pop up message is displayed (with no data results):

    ""Microsoft ODBC SQL Server Driver Timeout expired"

    However, if I run the exact same view in Query Analyser, it runs immediatelly with no problems (execution time = 112). The db server timeout is set at 0 (unlimited).

    Hope someone can help.

    Many thanks. Jeff

  • October 8, 2004 at 7:52 am

    #525946

    From another forum:

     

    "

    Hi!

    I'm having a really strange behaviour using ASP/ODBC/SQL Server 2000...

    I have a table width a 'text' type collumn.

    I have no problem inserting a new line with a long string (about 50k) to that column of the table using a adodb.recordset.

    But if I try to update it, with the exact same string I get a:

    Microsoft OLE DB Provider for ODBC Drivers error '80040e31'

    [Microsoft][ODBC SQL Server Driver]Timeout expired

    After waiting 40 seconds...

    If I run the exact some update in Query Analyser, it runs immediatelly with no problems (in about 30ms!!).

    This problem only occurs when the string is very big...

    Can anyone help me?

    Thanks!

    Pedro"

    ----------------------------------
     
    A1: "You should place the text column in a separate table and reference it by an id."

     
    A2: "This is depends on the width of your table. Microsoft doesn't like a record with more than 2 fields, that sum over 8000 bytes in it for an insert or update.. By placing this in a table by itself, the MS ignores thier own rule."
     
    A3:  "With some versions of MDAC you need to put text and image columns at the end of your select statement. Also, you should immediately copy the text data to a local variable if you need to reference it more than once in your code."
     
    A4:  "I had a similiar situation. I have a table with one text (16) -type column and multiple other shorter columns.

    When I ran two SQL queries the first one would succeed and the second one would fail on the ODBC time-out error.

    The funny thing was that the reference to the text-column was only made in the FIRST query and not in the second one.

    When I removed the reference to the text-column from the first query and fetched it's value in a third query after the second query was completed, everything started working perfectly again."

     
    HTH
     
    Mike Irwin

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply