DBAs, developers, and anyone else curious about how isolation levels can affect the performance and accuracy of a query.
The ability for multiple processes to query and update a database concurrently has long-been a hallmark of database technology, but this feature can be implemented in many ways. This session will explore the different isolation levels supported by SQL Server and Azure SQL Database, why they exist, how they work, how they differ, and how In-Memory OLTP fits in. Demonstrations will also show how different isolation levels can determine not only the performance, but also the result set returned by a query. Additionally, attendees will learn how to choose the optimal isolation level for a given workload, and see how easy it can be to improve performance by adjusting isolation settings. An understanding of SQL Server’s isolation levels can help relieve bottlenecks that no amount of query tuning or indexing can address – attend this session and gain Senior DBA-level skills on how to maximize your database’s ability to process transactions concurrently.
Why I Want to Present This Session:
This topic came from my desire to find a way to easily describe these seemingly-complex issues which can affect any database workload.
Latest posts by Bob (see all)
- Locks, Blocks, and Snapshots: Maximizing Database Concurrency - September 6, 2019