Skip to content

Details

OLTP databases can be constantly written to and even reporting databases are written to at least periodically. In order to ensure consistent results, connections must be isolated from one another while executing, ideally with the lowest possible cost to concurrency. How this isolation is handled is based on the isolation level, whether the classic lock based or the newer optimistic scheme of the in-memory OLTP engine is used, and even if both engines are enlisted in the same transaction. In this session we will look at examples of how SQL Server isolates reading and writing operations from other writing operations to explore how this may affect your application through error messages and performance hits

This Month's Speaker :
Speaker: Louis Davidson
Bio:

Louis Davidson has worked in the IT industry for over 20 years as a corporate database developer and architect. He has been a Microsoft SQL Server MVP for 15 years and has written six books on database design and other SQL Server topics. He has a bachelor’s degree in Computer Science from the University of Tennessee at Chattanooga. You can read more about Louis at drsql.org.

HRSSUG Monthly Meeting : Matters of Concurrency
Nov 18, 2020 6:30 PM - 8:00 PM (EDT)

Register
https://attendee.gotowebinar.com/register/293686563289857291

Members are also interested in