What is a characteristic of Snowflake's transaction locking and concurrency modeling?
According to the Snowflake documentation1, Snowflake uses a multi-version concurrency control (MVCC) model, which means that each transaction operates on a consistent snapshot of the database at a point in time. This allows queries and DML statements to run concurrently without blocking each other, as they do not modify the same data. Therefore, a deadlock, which occurs when concurrent transactions are waiting on resources that are locked by each other, cannot happen in Snowflake. Option B is incorrect because queries and DML statements do not block each other in Snowflake, unless they are explicitly started transactions and multiple statements in each transaction2. Option C is incorrect because transaction locking in Snowflake is enforced at the partition level, not the row or table level3. Option D is incorrect because queries executed within a given transaction do not see that transaction's uncommitted changes, but only the committed changes that occurred before the transaction started1.
Buddy
4 months agoRoxane
5 months agoChantell
5 months agoVeronika
5 months agoArlene
5 months agoFrancesco
6 months agoBecky
6 months agoNana
6 months agoTori
6 months agoRosina
6 months agoMiles
6 months agoMaile
6 months agoReena
6 months agoLynelle
6 months agoTish
6 months agoTayna
6 months agoAlberta
6 months agoLeonard
6 months agoBonita
7 months agoLeonora
2 years agoAntonio
2 years agoFernanda
2 years agoShantell
2 years agoCornell
2 years agoKarol
2 years agoEdmond
2 years agoNiesha
2 years ago