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