From the course: Designing Database Solutions for SQL Server 2016
Join today to access over 23,300 courses taught by industry experts.
Locking and concurrency strategy - SQL Server Tutorial
From the course: Designing Database Solutions for SQL Server 2016
Locking and concurrency strategy
- [Instructor] When two or more users access the same tables at the same time, they're considered concurrent users. If the operations that they are performing are simple reads, then SQL Server can easily accommodate both users simultaneously. But once one or more users begin updating and inserting records into a table that someone else is reading, things start to get a little bit more complicated. SQL Server 2016 provides a number of ways to manage concurrent data access. Before we take a look at how to design a concurrency strategy, it's important to better understand the problems that can arise so that we know to deal with them. Without any concurrency controls in place, users might experience lost updates, uncommitted dependencies, or what's known as a dirty read, inconsistent analysis, or a nonrepeatable read, phantom reads, or missing and double reads caused by row updates. Let's take a look at what each of these issues looks like and how to mitigate against them. A lost update…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.