A while back I was involved in an email thread where people were wondering about some ‘weird’ behavior from SQL Server. The problem was occurring on SQL Server 2016 and used the default isolation level of read committed. The scenario was as follows: Create a table with a few columns Batch 1: In one SSMS window, [&]

The post Read committed doesnt guarantee much& appeared first on Paul S. Randal.

http://feedproxy.google.com/~r/PaulSRandal/~3/dtpqd_OwfHk/