Home Forums SQL Server 2008 T-SQL (SS2K8) Is there a way to improve this SELECT statement for performance? RE: Is there a way to improve this SELECT statement for performance?

  • August 30, 2013 at 2:17 pm

    #1646488

    Sean Lange (8/30/2013)

    ScottPletcher (8/30/2013)

    NOLOCK can be useful, for example, for code lookup tables, such as state code lookups. A state hasn't been added since 1959, I think I'll risk it :-).

    And a table with 50 rows that hasn't been updated since 1959 is likely to encounter locking???

    No, but ANY locking ADDS OVERHEAD. Avoiding the locking thus reduces overhead.

    I don't know why so many want to deny that: THAT'S the main reason NOLOCK is available, to allow one to reduce locking overhead.

    SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.