SQL SERVER 2005 Drops ODBC Connection

  • We recently went live with an implementation of MS Dynamics Great Plains on SQL Server 2005. The app had been running fine on SQL Server 2000. Now user ODBC connections are dropped with no warning or message. The spid is then reassigned to a new login by SQL Server. The application has no idea that the original user is no longer connected to the spid.

    Does anyone have an idea as to why this is happening and a way to fix it?

    Thank you in advance for any insight you might have.

    Ellen

  • Cross-posting.

    Please continue conversation here

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

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

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