Every SQL Server developer has heard it: « Don’t use NOLOCK in production! » But this common rule isn’t as simple as it seems. Sometimes, what seems like a bad practice can actually be the right choice.
Let’s explain what NOLOCK really does in simple terms. When you use NOLOCK, you’re telling SQL Server « just show me what’s there right now, even if it might change in a second. » you could compare it to looking at your bank account while transactions are still processing – the numbers you see might not be final, but you get them right there and then.
Here’s