Posted By: TrickyNixon
I guess the real question is:
If I don’t care about dirty reads, will adding the with (NOLOCK) hint to a SELECT statement affect the performance of:
- the current SELECT statement
- other transactions against the given table
Select * from aTable with (NOLOCK)
1) Yes, a select with
NOLOCK will complete faster than a normal select.
2) Yes, a select with
NOLOCK will allow other queries against the effected table to complete faster than a normal select.
Why would this be?
NOLOCK typically (depending on your DB engine) means give me your data, and I don’t care what state it is in, and don’t bother holding it still while you read from it. It is all at once faster, less resource-intensive, and very very dangerous.
You should be warned to never do an update from or perform anything system critical, or where absolute correctness is required using data that originated from a
NOLOCK read. It is absolutely possible that this data contains rows that were deleted during the query’s run or that have been deleted in other sessions that have yet to be finalized. It is possible that this data includes rows that have been partially updated. It is possible that this data contains records that violate foreign key constraints. It is possible that this data excludes rows that have been added to the table but have yet to be committed.
You really have no way to know what the state of the data is.
If you’re trying to get things like a Row Count or other summary data where some margin of error is acceptable, then
NOLOCK is a good way to boost performance for these queries and avoid having them negatively impact database performance.
Always use the
NOLOCK hint with great caution and treat any data it returns suspiciously.