Post reply

Error message when you try to change a column of a table by using the ALTER TABLE statement in SQL Server 2005

  • January 13, 2009 at 12:34 am

    #217426

    I am hitting the below error when trying to alter a table in SQL Server 2005:

    Msg 109, Level 20, State 0, Line 0

    A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)

    I have found a article in microsoft(http://support.microsoft.com/kb/916780) stating that this is a known error and need to apply SQL Server Service Pack 3 inorder to rectify the problem but after I installed and restarted the server, I am still hitting the same Error.

    Could anyone please help me resolving this error? Thank you in advance.

  • January 13, 2009 at 12:47 am

    #925682

    Check the SQL error log. The message just indicates that your query has been forcefully disconnected. That's usually the result of the connection been killed by someone, or the result of hitting a severity 19 or higher error.

    Either way, there will be something in the SQL error log.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • January 13, 2009 at 1:18 am

    #925694

    Thanks for the input, I will check the SQL Error Log then.

    But what I don't understand is, I have tried to run the same SQL script to a different

    SQL 2005 Server but I did not hit the error and it was successfully executed.

  • January 13, 2009 at 7:28 am

    #925867

    jonathan (1/13/2009)

    But what I don't understand is, I have tried to run the same SQL script to a different

    SQL 2005 Server but I did not hit the error and it was successfully executed.

    Why's that a surprise? There's something wrong here that's causing a disconnection. Whatever it is probably is not also wrong with the other server. Until we find out what cause the disconnection, there's no point wondering.

    I doubt this is a SQL bug that you've hit, I have a couple other suspicions though.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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