• You determine whether your IO config is at fault well after looking at other, simper things. Like lack or indexes or badly written queries (most commonly the cause of slow performance)

    And adding nolock is NOT a performance tuning method. It's telling SQL that incorrect (duplicate/missing) data is acceptable and hence it's allowed to not lock data its reading.

    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