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.
Jennie
3 months agoKimberlie
2 months agoElinore
2 months agoCarline
2 months agoChauncey
3 months agoMatt
3 months agoDelbert
2 months agoLynelle
2 months agoTimothy
2 months agoAlita
3 months agoAndree
3 months agoChauncey
3 months agoAmber
3 months agoLisha
2 months agoKasandra
2 months agoRonald
3 months agoStephaine
3 months agoEmilio
3 months agoOren
3 months agoHermila
3 months ago