John Deardurff enables a feature:
Modern SQL Server workloads demand high concurrency without sacrificing consistency. Traditionally, we relied on locking to enforce correctness, but that came with blocking and performance challenges. To resolve some of these issues, row versioning was used to reduce some of that contention overhead. But now with optimized locking in SQL Server 2025, we have a more efficient and scalable concurrency model.
Click through for a demo. My point of curiosity is, what’s the impact in a practical but busy environment? I don’t have one of those running SQL Server 2025, so I do wonder when we’ll get the tell-all post from someone in a very busy environment who has it on. (Or, if we already have and I’ve missed it, please do let me know!)
From a practical standpoint, I sort of don’t care if it has a profound impact. I just hope it serves to further legitimize RCSI, which for some absurd reason still needs legitimizing to SQL Server people.
That’s fair. RCSI has been my mental default for so long that I get annoyed when I hop into a new environment and see that it is still off.