Home Forums SQL Server 2005 SQL Server 2005 General Discussion A severe error occurred on the current command.The results, if any, should be discarded. RE: A severe error occurred on the current command.The results, if any, should be discarded.

  • February 15, 2013 at 12:55 am

    #1588210

    tony28 (2/14/2013)

    Hi Gila, please can you help me? I have test server, and I inserted lot of rows for test with NOLOCK hint and then i got first error

    Msg 9002, Level 17, State 2, Line 1

    The transaction log for database 'MCS_BIDB' is full due to 'LOG_BACKUP'.

    Switch the DB to simple recovery or take a log backup. That's not database corruption, that's a full transaction log

    Please read through this - Managing Transaction Logs[/url]

    Also, ditch that nolock hint. It has no effect on inserts.

    See - http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx

    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