This document discusses the side effects of using NOLOCK hints in SQL queries. It notes that NOLOCK is not an acceptable way to fix locking issues and risks corrupting data. The document recommends researching SNAPSHOT ISOLATION as an alternative and provides contact information for Jason Strate, a database architect, who discusses locking and isolation levels on his website.

1. Jason Strate
Database Architect
Pragmatic Works, Inc.
THE SIDE EFFECT
OF NOLOCK

2. WWW.JASONSTRATE.COM

3. WE NEED SPEED!

4. THE PROBLEM!
http://bit.ly/18yv3tnhttp://www.flickr.com/photos/oxborrow

5. THE DATA OF BOB AND FRED

6. THE DATA OF BOB AND FRED

7. THE DATA OF BOB AND FRED

8. THE DATA OF BOB AND FRED
NO ROOM!

9. THE DATA OF BOB AND FRED
PAGE
SPLIT

10. THE DATA OF BOB AND FRED
WHAT?!

11. THE DATA OF BOB AND FRED
WHAT?!

12. Demo 1
NOLOCK
DEMO

13. 1. NOLOCK is not an
acceptable locking fix.
2. You are risking yours
and other people’s data.
3. Troubleshooting is
impossible.
4. Research SNAPSHOT
ISOLATION level
SUMMARY

14. Jason
Strate
e: jstrate@pragmaticworks.com
e: jasonstrate@gmail.com
b: www.jasonstrate.com
t: StrateSQL
Related
Content
www.jasonstrate.com/tag/locking
RESOURCES