Alles gut es ist noch nicht nolock november
September 28, 2026 at 3:35 PM
Alles gut es ist noch nicht nolock november
I put NOLOCK on all the reports.
Now they are fast and occasionally fiction.
Row versioning gets you the fast part without the creative writing.
Read Committed Is Cruel by Default: my session at #PASSDataSummit West.
passdatacommunitysummit.com/west/
Now they are fast and occasionally fiction.
Row versioning gets you the fast part without the creative writing.
Read Committed Is Cruel by Default: my session at #PASSDataSummit West.
passdatacommunitysummit.com/west/
September 22, 2026 at 6:02 PM
I put NOLOCK on all the reports.
Now they are fast and occasionally fiction.
Row versioning gets you the fast part without the creative writing.
Read Committed Is Cruel by Default: my session at #PASSDataSummit West.
passdatacommunitysummit.com/west/
Now they are fast and occasionally fiction.
Row versioning gets you the fast part without the creative writing.
Read Committed Is Cruel by Default: my session at #PASSDataSummit West.
passdatacommunitysummit.com/west/
The year is 2026. The world is controlled by Claude. Claude knows about parameter sniffing so it uses MAXDOP 1 WITH NOLOCK RECOMPILE.
September 15, 2026 at 1:43 PM
The year is 2026. The world is controlled by Claude. Claude knows about parameter sniffing so it uses MAXDOP 1 WITH NOLOCK RECOMPILE.
AI loves NOLOCK
September 15, 2026 at 1:17 PM
AI loves NOLOCK
“But NOLOCK won’t hurt me if I’m using an index!”
NOLOCK is bad and you probably shouldn't use it, but every time I mention that publicly, the pushback just keeps coming. I don't know why people so firmly believe that their situation couldn't possibly be affected by bad/random data from NOLOCK.…
NOLOCK is bad and you probably shouldn't use it, but every time I mention that publicly, the pushback just keeps coming. I don't know why people so firmly believe that their situation couldn't possibly be affected by bad/random data from NOLOCK.…
“But NOLOCK won’t hurt me if I’m using an index!”
NOLOCK is bad and you probably shouldn't use it, but every time I mention that publicly, the pushback just keeps coming. I don't know why people so firmly believe that their situation couldn't possibly be affected by bad/random data from NOLOCK. Today's misconception comes from a LinkedIn commenter telling me it's safe to use if you're doing index seeks. Hoo boy.
www.brentozar.com
September 15, 2026 at 1:15 PM
“But NOLOCK won’t hurt me if I’m using an index!”
NOLOCK is bad and you probably shouldn't use it, but every time I mention that publicly, the pushback just keeps coming. I don't know why people so firmly believe that their situation couldn't possibly be affected by bad/random data from NOLOCK.…
NOLOCK is bad and you probably shouldn't use it, but every time I mention that publicly, the pushback just keeps coming. I don't know why people so firmly believe that their situation couldn't possibly be affected by bad/random data from NOLOCK.…
The SET Succeeds and the Catalog Read Succeeds, Then Msg 3951
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they […]
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they […]
Original post on chaosfem.tw
chaosfem.tw
September 13, 2026 at 2:10 PM
The SET Succeeds and the Catalog Read Succeeds, Then Msg 3951
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they […]
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they […]
The SET Succeeds and the Catalog Read Succeeds, Then Msg 3951
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they read…
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they read…
The SET Succeeds and the Catalog Read Succeeds, Then Msg 3951
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they read was actually committed. Adopting it has two prerequisites that are easy to get wrong, and both fail in ways that point somewhere other than the cause.
www.sqlserverscience.com
September 13, 2026 at 2:10 PM
The SET Succeeds and the Catalog Read Succeeds, Then Msg 3951
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they read…
Snapshot isolation is the answer to most of the problems WITH (NOLOCK) gets used for, which I covered in NOLOCK Returned a Balance That Never Existed. Readers stop waiting for writers, and unlike read uncommitted, everything they read…
NOLOCK Returned a Balance That Never Existed
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real […]
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real […]
Original post on chaosfem.tw
chaosfem.tw
September 12, 2026 at 2:15 PM
NOLOCK Returned a Balance That Never Existed
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real […]
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real […]
NOLOCK Returned a Balance That Never Existed
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real Two…
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real Two…
NOLOCK Returned a Balance That Never Existed
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real Two connections against the same instance. An account table with one row, holding 100.00. Connection A opens a transaction and changes the balance, then stops without committing:
www.sqlserverscience.com
September 12, 2026 at 2:15 PM
NOLOCK Returned a Balance That Never Existed
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real Two…
WITH (NOLOCK) gets added to queries for one reason: something was slow, or something was blocked, and the hint made the query run. It does make blocking stop. What it gives up in exchange is arguably far more important. A balance that was never real Two…
Reading: animation of why NOLOCK counts rows twice and skips rows: blog.sqlauthority.com/2026/09/04/n...
NOLOCK: Why It Counts Some Rows Twice and Misses Others - SQL Authority with Pinal Dave
NOLOCK is not a safe performance fix, it is a decision to reduce blocking by accepting an answer that may never have been true. The whole problem is that nobody who types it thinks they are making…
blog.sqlauthority.com
September 8, 2026 at 1:25 AM
Reading: animation of why NOLOCK counts rows twice and skips rows: blog.sqlauthority.com/2026/09/04/n...
Link of items I'm selling on eBay, it out!
#eBaySeller #Wizman02 #Auction #eBayFinds #PaBoom #CareForColombia #Charity #Doninger #No1981-01 #Brass #U.S.PostOffice #P.O.MailBox #Door #w/Glass #NoLock
Doninger No1981-01 Brass U.S. Post Office P.O. Mail Box Door w/Glass but No Lock
ebay.io/m/WcZQuE
#eBaySeller #Wizman02 #Auction #eBayFinds #PaBoom #CareForColombia #Charity #Doninger #No1981-01 #Brass #U.S.PostOffice #P.O.MailBox #Door #w/Glass #NoLock
Doninger No1981-01 Brass U.S. Post Office P.O. Mail Box Door w/Glass but No Lock
ebay.io/m/WcZQuE
September 1, 2026 at 1:55 AM
Link of items I'm selling on eBay, it out!
#eBaySeller #Wizman02 #Auction #eBayFinds #PaBoom #CareForColombia #Charity #Doninger #No1981-01 #Brass #U.S.PostOffice #P.O.MailBox #Door #w/Glass #NoLock
Doninger No1981-01 Brass U.S. Post Office P.O. Mail Box Door w/Glass but No Lock
ebay.io/m/WcZQuE
#eBaySeller #Wizman02 #Auction #eBayFinds #PaBoom #CareForColombia #Charity #Doninger #No1981-01 #Brass #U.S.PostOffice #P.O.MailBox #Door #w/Glass #NoLock
Doninger No1981-01 Brass U.S. Post Office P.O. Mail Box Door w/Glass but No Lock
ebay.io/m/WcZQuE
Sadly, I think my "fix" is going to be NOLOCK. 😭 Or at least my first try.
July 6, 2026 at 9:00 PM
Sadly, I think my "fix" is going to be NOLOCK. 😭 Or at least my first try.
You really know you’re looking at some legacy shit when you see a WITH(NOLOCK) in a sql query
June 15, 2026 at 6:54 PM
You really know you’re looking at some legacy shit when you see a WITH(NOLOCK) in a sql query
So you can either have reports that take a long time to run and **are right**, or use NOLOCK and silently return old or incorrect data in situations that would have caused a lock and have it quick instead.
Infra can shout at me, then. I work in data and I want my reports to be right, please.
Infra can shout at me, then. I work in data and I want my reports to be right, please.
May 21, 2026 at 9:18 AM
So you can either have reports that take a long time to run and **are right**, or use NOLOCK and silently return old or incorrect data in situations that would have caused a lock and have it quick instead.
Infra can shout at me, then. I work in data and I want my reports to be right, please.
Infra can shout at me, then. I work in data and I want my reports to be right, please.
NOLOCK my beloved, it is that time again, let me bask in the glory of your total superfluousness
There was a dev before me whose work I periodically need to update and they were clearly trained on massive transaction db's because even the simplest select queries are always full of NOLOCK.
May 19, 2026 at 2:29 PM
NOLOCK my beloved, it is that time again, let me bask in the glory of your total superfluousness
I've never seen a LEFT JOIN written as a CTE, used in another CTE before.
With the 2nd CTE reading like a recursive one (anchor stmt, union all, recursive stmt) with NOLOCK **AND** index hint.
1. Don't do that
2. If you call the 1st CTE in both parts of the recursive CTE, then its not recursive!!
With the 2nd CTE reading like a recursive one (anchor stmt, union all, recursive stmt) with NOLOCK **AND** index hint.
1. Don't do that
2. If you call the 1st CTE in both parts of the recursive CTE, then its not recursive!!
April 16, 2026 at 4:30 PM
I've never seen a LEFT JOIN written as a CTE, used in another CTE before.
With the 2nd CTE reading like a recursive one (anchor stmt, union all, recursive stmt) with NOLOCK **AND** index hint.
1. Don't do that
2. If you call the 1st CTE in both parts of the recursive CTE, then its not recursive!!
With the 2nd CTE reading like a recursive one (anchor stmt, union all, recursive stmt) with NOLOCK **AND** index hint.
1. Don't do that
2. If you call the 1st CTE in both parts of the recursive CTE, then its not recursive!!
I have found that the mixed message of using NOLOCK *anywhere* is not worth it even for 500 GB reporting databases. If you have a readable secondary give that to the report developer and when it doesn't work for them because they are writing back to the database, tell me how the report is read only.
April 10, 2026 at 11:10 AM
I have found that the mixed message of using NOLOCK *anywhere* is not worth it even for 500 GB reporting databases. If you have a readable secondary give that to the report developer and when it doesn't work for them because they are writing back to the database, tell me how the report is read only.
I once worked for a company who insisted I sprinkled NOLOCK over everything. Even though I showed them it was bad, and begged them to reconsider.
April 10, 2026 at 8:42 AM
I once worked for a company who insisted I sprinkled NOLOCK over everything. Even though I showed them it was bad, and begged them to reconsider.
Skip WITH NOLOCK.
Database level READ UNCOMMITTED is the way
Database level READ UNCOMMITTED is the way
April 10, 2026 at 4:30 AM
Skip WITH NOLOCK.
Database level READ UNCOMMITTED is the way
Database level READ UNCOMMITTED is the way
I'd really rather not have to keep running these demos for clients as often as I do, but here we are again. NOLOCK Is Bad And You Probably Shouldn’t Use It: www.brentozar.com/archive/2021...
NOLOCK Is Bad And You Probably Shouldn't Use It. - Brent Ozar Unlimited®
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…
www.brentozar.com
April 10, 2026 at 1:25 AM
I'd really rather not have to keep running these demos for clients as often as I do, but here we are again. NOLOCK Is Bad And You Probably Shouldn’t Use It: www.brentozar.com/archive/2021...
Claude recommended WITH NOLOCK
April 9, 2026 at 5:16 PM
Claude recommended WITH NOLOCK
whichever one of you left your old job and had a job that said "restore database (x) with (nolock)" should be ashamed of yourselves
April 7, 2026 at 8:10 PM
whichever one of you left your old job and had a job that said "restore database (x) with (nolock)" should be ashamed of yourselves
He needs to query with(nolock)
March 26, 2026 at 6:02 PM
He needs to query with(nolock)