Pipeline Change History
Each pipeline keeps an immutable, time-ordered history of every configuration change, showing what changed, when it changed, and who made the change.
Read moreEach pipeline keeps an immutable, time-ordered history of every configuration change, showing what changed, when it changed, and who made the change.
Read moreSelect Skip backfill when adding a new table to an existing pipeline to start streaming new CDC changes without a historical load.
Read morePause replication for a single table while the rest of the pipeline keeps streaming, with changes held in Kafka and reminders sent after two days.
Read moreTable change alerts are consolidated into one notification per connector or database instead of one per pipeline.
Read moreThe Pipeline Overview lists every replicated table in a pipeline with search, schema and status filters, and live status metadata.
Read morePipelines can be created and managed in separate environments such as dev, staging, and production, each with its own scoped connectors and resources.
Read moreBackfills of fanned-in tables can target specific source schemas instead of backfilling every schema that feeds the destination table.
Read moreA view only role gives stakeholders read-only dashboard access to see pipelines and sync status without changing settings or configurations.
Read morePipeline alerts and notifications, including replication status and schema changes, can be delivered to Microsoft Teams alongside email and Slack.
Read moreAdd static columns to an existing pipeline to tag replicated rows in the destination table with metadata such as region or environment.
Read more