Performance and Tuning

SQLServerCentral Article

The Paradox of NOLOCK: How Dirty Reads Can Sometimes Be Cleaner

  • Article

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 […]

(9)

You rated this post out of 5. Change rating

2024-12-09

5,124 reads

Blogs

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Designing a Storage Load Test for SQL Server

By

I’ve been doing storage load tests for SQL Server for a long time, both...

Read the latest Blogs

Forums

How Long is a Long I/O?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Long is a Long...

T-SQL Trigonometric Functions in SQL Server

By Imran2629

Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...

Half of All Engineers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Half of All Engineers

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers