Two Of My Favorite NOLOCK Demos from Paul White and Aaron Bertrand

[@vasylpavuk391]

This format of shorts is great. Thank you.

[@ErikDarlingData]

Ah, thanks. I wish I had more short topics to talk about, heh.

[@Garstor]

Hey! I'm Canadian, too! Still a proud reservist in the Darling Data Army though.

[@ErikDarlingData]

🫡🍟

[@stephenlawrenson2380]

We are encountering a race condition in Azure SQL. Many devices writing many records, and then on prem wanting to pull them records down by identity from last pull. Had one record skipped!! Nice race condition. I have countered the devs to use a dtg column to introduce stability windows. The developer muted setting read committed on the DB. My response was “I own guns” 😂😂😂

[@ErikDarlingData]

are you not using the OUTPUT clause for this?

[@stephenlawrenson2380]

@ from running a delete to serialise it out? The events are still required to exist in azure after being pulled down as they are required to be queried for other processes!!

[@ErikDarlingData]

you can use OUTPUT from any modification, not just deletes. DECLARE @t table ( id bigint IDENTITY PRIMARY KEY, c1 date NOT NULL ); INSERT @t ( c1 ) OUTPUT Inserted.* VALUES ('20241211');

[@curtisbragdon5194]

@@ErikDarlingData I had to do this a few months back. Thanks for the demos. I will add them to my Baker's Dozen of bad query design demos for our Developers/DBAs

[@BrandonChampion]

My favorite Aaron Bertrand NOLOCK demo is where he shows (admittedly a very contrived) scenario where it can return values that never actually existed in the table. kzbin.info/www/bejne/gYPPg56Qn5Wia5osi=6QpvnSv0xQ1-Jzwg&t=4606

[@ErikDarlingData]

Oh I had forgotten about that one!