Home Forums SQL Server 7,2000 T-SQL Strange Behavior with (nolock) RE: Strange Behavior with (nolock)

  • October 22, 2013 at 3:13 pm

    #1660731

    GilaMonster (10/22/2013)

    DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    I'd still remove the nolocks, they definitely can cause you problems, by design they can result in incorrect data. As I said, not usually this incorrect though.

    Heh... to be sure, I absolutely agree. I wasn't suggesting to leave the nolocks in place. I've just never seen such a large problem with it before.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)