Post reply

ODBC Connection dropped

  • June 29, 2009 at 10:49 am

    #133492

    I have a user with a client application that is using an ODBC connection to a SQL database. Application does some changed on the tables that another web application may use to view the records.

    There is also an importing process that reads those "client application" tables and updates records in some other tables.

    Almost every day in the afternoon client's ODBC connection get lost and a user loses all the job.

    Can it be that some session expired? But in the morning user and leave computer for more than 20 min and come back and still able to save the work. Can it be that for some reason database load is too heavy? Is it a database problem or application(s) problem?

    What can be the reason and where to look for answers?

  • June 29, 2009 at 12:03 pm

    #1017033

    there's a pretty good thread on the issue here, but it may or may not be the same thing you are experiencing:

    http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/ef029812-45d0-4544-a00f-bd9e66a6d4bf

    it seems the default behavior of SQL 2005 changed, and that also some networking objects, like routers, sometimes do not pass along "Keep Alive" messages sent to teh client machines to check if they are still connected.

    Hope that helps!

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • June 29, 2009 at 12:22 pm

    #1017124

    Thanks,

    I will investigate this. You are correct, it's remote SQL Server 2005 and a legacy application with ODBC connection

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

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