Azure SQL Database: Non-blocking transactions | Azure Friday

Managing concurrent access to a resource, be it a row, a table, or a single value, is easy if no one is trying to modify the underlying data. But what happens if someone changes data while someone else is reading it? Even better, what could happen if two or more users try to change the same data at the same time? Well, there are a couple of options. The easiest is to just ask everyone to queue up, the other is to have multiple versions of the data available over time so that no one must wait for the changes to be finished. Let's explore both the options with Lara Rubbelke and Davide Mauri on Azure Friday.

Chapters
00:00 – Introduction
01:50 – DEMO: Locking behavior
03:20 – DEMO: Default "read committed snapshot" behavior
05:20 – Migrating from SQL Server to Azure SQL DB
06:42 – DEMO: snapshot isolation level
12:12 – Wrap-up

Recommended resources

Connect with us

#MicrosoftAzure #AzureFriday #AzureSQL

[danielegiovanetti]

Davide you are fantastic! Thanks Azure Friday for sharing these precious info

[cvetkovicslobodan]

Great presentation Davide!
What about if the second transaction is also updating data, and the first one is committed before the second one?
I would assume the second operation fails as data is changed in the meantime (e.g. by comparing sequence numbers at the beginning and at the commit phase)? The solution for a second transaction is probably a retry.

[RtoipKa]

I thought that this was the only allowed setting in Azure SQL. How can we turn it off? Just curious.

[jacobdreyerlund]

Is this also enabled by default for azure sql managed instance?