ScottPletcher (8/30/2013)

---

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

Sean Lange (8/30/2013)

---

ScottPletcher (8/30/2013)

---

Sean Lange (8/30/2013)

NOLOCK hints. They are NOT a performance boost.

To me, that's not a logical claim. While NOLOCK is clearly dangerous, it DOES in fact reduce overhead by avoiding any locks at all from being taken while reading the table.

Good grief Scott. How many times have you seen or heard people say they add NOLOCK because "it makes the queries faster"? Using NOLOCK as a performance enhancement tool for queries is like using a jet engine for cooking fish. Sure it will get you to the end line slightly faster but it has a really good chance of destroying the food.

Are you honestly suggesting that we should use this to boost performance or do you just like splitting hairs? I provided some links with in depth details about the usage of that hint. I would assume that somewhat alleviates the need for me to reproduce all the details in my thread.

Yes, I am honestly suggesting it can be worthwhile to add NOLOCK to boost performance. Are you honestly suggesting it should be removed from the product just because you don't understand when it is safe or not safe to use it??

Yes I am. I would use isolation which does not return duplicate/missing data unlike NOLOCK.

Huh? The only isolation level lower than the default is READ UNCOMMITTED, which is just shorthand for NOLOCK on every table.