Defeat Page Latches in Microsoft SQL Server with Torsten Strauß

Concurrent inserts into a clustered table with an ever-increasing key become a bottleneck since Microsoft SQL Server must protect the corresponding pages with a page latch. There are several techniques like, hash partitioning, reserve bits, in-memory OLTP and the feature introduced in 2019 CTP 3.1 called OPTIMIZE_FOR_SEQUENTIAL_KEY. We will compare these features to understand their performance improvements and the effort required to modify your existing application.

Bio
Torsten (MVP, MCSE, MCT) has been working with Microsoft SQL Server since the turn of the millennium and is specialized in performance optimization for large SQL Server environments.

He has been with bp as a database engineer for over two decades and collaborates closely with Sarpedon Quality Lab as a Principal Microsoft SQL Server Consultant.

Torsten has been recognized as a Microsoft Most Valuable Professional for Data Platform since 2018.