When to Choose Snowflake for CDC Final State

May 2026

Choose Snowflake for CDC final state when you want Snowflake to own the reconciled table and the documented MERGE-based apply path matches your warehouse plan.

Short Answer

Choose Snowflake when you want the final-state tables in Snowflake and you want Skippr to apply CDC with Snowflake MERGE semantics. The documented destination contract is direct: Skippr adds _skippr_order_token, compares incoming and existing order tokens during upsert, and creates companion tombstone tables so deletes remain authoritative.

Snowflake is especially straightforward in the docs because the CDC behavior does not require a separate destination-specific reconciliation pattern beyond that MERGE contract. You still need the documented database, schema, warehouse, role, and authentication setup, but the warehouse-side CDC story is concise and explicit.

Why Teams Struggle with This

Teams sometimes talk about Snowflake as if storage alone solves CDC. It does not. What matters is that the destination docs spell out how newer changes win and how deletes remain durable across retries and replays.

• Final-state correctness still depends on an explicit business key per logical row.
• A replayed older change must lose during MERGE, which is why the order-token guard exists.
• Deletes need tombstones so a later replayed insert does not silently restore a row that should stay deleted.
• Snowflake still requires the documented grants on the warehouse, database, and raw schema.

How Skippr Handles It

Skippr is a good fit for Snowflake because the product and docs keep the CDC contract concrete. The same workflow that captures changes also creates the warehouse structures needed for final-state reconciliation.

The staging story is documented too. Skippr uses Snowflake internal staging by default and exposes the staging controls directly when you want to override that path, so the team can choose Snowflake without guessing how the load path behaves.

• Snowflake CDC is documented as exactly-once final-state MERGE semantics.
• Internal staging is the default path, with documented controls for external staging when needed.
• Order-token columns and tombstone tables are created automatically.
• Key-pair authentication is documented and recommended, especially when MFA is enforced.

What the First Useful Version Looks Like

Choose Snowflake when Snowflake is where you want the final-state table to live and the documented MERGE-and-tombstone contract is the behavior you want the warehouse to enforce.

That keeps the CDC discussion focused on table correctness instead of turning the destination into a black box.