NOLOCK Is Bad And You Probably Shouldn’t Use It.

I’m waiting for the YOLOck option.

When you put NOLOCK in your query, SQL Server will:

Read rows twice Skip rows altogether Show you changes that never actually got committed Let your query fail with an error

This is not a bug. This is by design. To understand what happens, read these blog posts in order:

Using NOLOCK? Here’s how you’ll get the wrong query results. “But NOLOCK is okay when my data isn’t changing, right?” “But surely NOLOCK is okay if no one’s changing data, right?”

After reading those, you’re going to ask, “So what am I supposed to do if