Post reply

Info requested on DB updates in a stateless environment

  • September 19, 2008 at 2:01 am

    #131369

    Hi there,

    For the first time ever I am looking at the problems of database updates in a stateless situation. I've read up on this subject, but would like to have some hands-on info on how to handle updates specifically for SQL Server.

    Currently we're thinking of using a DATETIME attribute to check if a record has been changed between SELECT and UPDATE action, but I have the nagging feeling this is far from fullproof against duplicate updates on the same record.

    Any thoughts? pointers to articles on this?

    Greetz,
    Hans Brouwer

  • September 19, 2008 at 2:09 am

    #874049

    Consider using a timestamp (aka rowversion). It's got nothing to do with time despite the name. It's a binary number that changes every time the row is updated is unique within the DB (I think)

    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 2 posts - 1 through 2 (of 2 total)

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