Avoid using NOLOCK on SQL Server UPDATE and DELETE statements
Occasionally I come across UPDATE and DELETE statements where the target SQL Server table is referenced with the NOLOCK hint. Does this hint help or hurt performance in this case?
2014-03-03
4,698 reads
