I've been nosing around--and I'm no DBA myself,--but became curious when trying to troubleshoot a particularly expensive (and infrequent) query that performs an outer join on a linked server (2k5 to 2k5, different dbs on different physical machines). The issue doesn't generally seem to be execution time, but rather locking, as the outer join is against a pretty massively read from/written to db, and was wondering if adding a NOLOCK hint to the join statement would be a futile gesture. I've been nosing around--and I'm no DBA myself,