3 ms·
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 seri
by brasetvik 3y ago
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?
- vore 3y agoOnly 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.
- bob1029 3y agoThere has been some recent improvement to locking behavior: https://learn.microsoft.com/en-us/sql/relational-databases/performance/optimized-locking https://learn.microsoft.com/en-us/sql/relational-databases/p...