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
3 months agoRoxane
3 months agoChantell
3 months agoVeronika
4 months agoArlene
4 months agoFrancesco
4 months agoBecky
4 months agoNana
4 months agoTori
5 months agoRosina
5 months agoMiles
5 months agoMaile
5 months agoReena
5 months agoLynelle
5 months agoTish
5 months agoTayna
5 months agoAlberta
5 months agoLeonard
5 months agoBonita
5 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