Hacker News Reader

Or from the other perspective of the trade-off: One caveat with MSSQL is that ALL concurrent transactions must pay the overhead if _some_ transactions need serializable guarantees?

View on HN

Only if they touch the same data. If they are touching disjoint sets of data then there is no overhead to be paid by non-SERIALIZABLE transactions.

There has been some recent improvement to locking behavior:

https://learn.microsoft.com/en-us/sql/relational-databases/p...

Reply on news.ycombinator.com