connect-cdc-sqlserver

You can stream SQL Server CDC changes to Kafka by configuring a CDC input with your database connection string and table include patterns, then running the pipeline to capture and route events to topics in real time.

Snapshot-then-stream lifecycle captures an initial snapshot of your SQL Server data before continuously streaming incremental CDC events, ensuring downstream systems have the full table state before applying real-time changes.

Yes, per-table routing allows you to stream SQL Server CDC changes from multiple tables into separate dedicated Kafka or Redpanda topics, keeping downstream data pipelines organized by source table.

Checkpointing tracks SQL Server CDC LSN positions using either built-in or external caches, allowing the pipeline to resume streaming from the last captured log sequence number without data loss after interruptions.

Yes, the SQL Server CDC input satisfies enterprise licensing requirements, enabling you to capture and stream change data capture events into Redpanda or Kafka for continuous enterprise data pipelines.

Yes, SQL Server CDC pipelines support configurable batching and backoff control settings to balance latency and database load, preventing overwhelming source systems during high-volume change data capture streaming.