Skippr Docs

Appearance

When to Choose Azure Synapse for CDC Final State ​

May 2026

Choose Azure Synapse for CDC final state when Synapse should own the reconciled table and the documented TDS-plus-MERGE destination path matches your environment.

Short Answer ​

Choose Azure Synapse when you want the final-state table in Synapse and you want Skippr to apply CDC with the documented MERGE pattern over a TDS connection. In this setup, Skippr creates the order-token column, creates tombstone tables, and uses the same final-state rules described across the CDC docs.

That is the right choice when the Synapse connection model, schema location, and write permissions already fit the team. The warehouse decision should be tied to the documented apply behavior, not just to the fact that Synapse can receive rows.

Why Teams Struggle with This ​

It is easy to reduce a destination decision to connection details. For CDC, that is incomplete. You also need to decide whether the destination apply contract is the one you want after retries, deletes, and replay.

  • Synapse final-state reconciliation still depends on business keys and comparable ordering.
  • The runner must be able to reach the Synapse endpoint over the configured TDS connection.
  • The Synapse login needs write access to the target schema so Skippr can create and manage the CDC tables.
  • Deletes still rely on tombstone handling, not on blind delete statements with no replay protection.

How Skippr Handles It ​

Skippr keeps the Synapse decision narrow and reviewable. The docs state that Synapse supports exactly-once final-state reconciliation via MERGE, and that the destination will receive the same automatic order-token and tombstone additions as other final-state warehouses.

That is useful because you can evaluate Synapse on documented behavior: TDS connectivity, schema permissions, and MERGE-based reconciliation. There is much less guesswork about what the warehouse is expected to do.

  • Azure Synapse CDC is documented as exactly-once final-state reconciliation via MERGE.
  • The connection model is explicit: an ADO-style connection string over TDS.
  • Order-token columns are created automatically for CDC-managed tables.
  • Tombstone tables are created automatically to keep deletes authoritative.

What the First Useful Version Looks Like ​

Choose Synapse when Synapse is already the warehouse where you want the reconciled table to live and the documented TDS-and-MERGE path is the one your team wants to operate.

If that fits, Synapse gives you a clear destination-side contract instead of a custom CDC apply story you would have to invent yourself.