From the course: Microsoft Azure Synapse for Developers

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Transactions in dedicated SQL pool

Transactions in dedicated SQL pool

From the course: Microsoft Azure Synapse for Developers

Start my 1-month free trial Buy for my team

Transactions in dedicated SQL pool

“

- [Instructor] As you might expect in SQL databases, dedicated SQL pools also support transactions. However, since the data warehouse is maintained at scale to ensure high-performance, some features are limited when compared to an SQL server. Dedicated pools implement ACID transactions. The default level is set to READ UNCOMMITTED. With this level, transactions will work and anything we changed will roll back. But these will also ensure the consistency of the queries while the transaction is going on, which means we can have dirty reads, non-repeatable reads, and phantom records. Currently, we can only change the transaction level to READ COMMITTED SNAPSHOT ISOLATION. Once we enable READ COMMITTED SNAPSHOT ISOLATION, all transactions in the data warehouse will be executed under this level. The idea behind READ COMMITTED SNAPSHOT ISOLATION is as following. Instead of locking a record during the reading phase with a shared…

Contents