SQL Server Performance

Query on NewsLetter

Discussion in 'Please Tell Us What You Think' started by gaurav_bindlish, Sep 24, 2003.

  1. gaurav_bindlish New Member

    On tables that experience high levels of updates, consider adding
    a timestamp column to the busy, if there isn't one already. A
    timestamp column helps SQL Server perform concurrency control
    more efficiently. If a timestamp column is not available, SQL
    Server must compare the values of all columns in a row to all of
    the current values in the row at the time of the update. [7.0,
    2000]

    Brad, I didn't understand this. Can you explain it to me?

    Gaurav
    Moderator
    Man thrives, oddly enough, only in the presence of a challenging environment- L. Ron Hubbard
  2. bradmcgehee New Member

    Part of the confusion is because of a typo, the tip should have read:

    On tables that experience high levels of updates, consider adding a timestamp column to the table, if there isn't one already. A
    timestamp column (or in 2000, the rowversion datatype) helps SQL Server perform concurrency control more efficiently. If a timestamp column is not available, SQL Server must compare the values of all columns in a row to all of the current values in the row at the time of the update. [7.0, 2000]

    In the SQL Server 2000 Books Online, you can find more information on this topic by searching on "rowversion data type" and "rowversion synonym for timestamp".



    -----------------------------
    Brad M. McGehee, MVP
    Webmaster
    SQL-Server-Performance.Com

Share This Page