Modern data teams are not short on tools. The challenge is coordinating reliable data movement across growing environments, tighter refresh windows, and increasingly complex architectures.
The Q1 product release (Version 26) for CData Sync focuses on that reality. This release introduces new coordination capabilities, expands support for open-table formats across warehouses and lakehouse platforms, lays a stronger foundation for automation, and improves execution and enterprise CDC coverage.
Coordinating data workflows with Pipelines
Sync Pipelines introduces lightweight workflow coordination directly inside Sync. Instead of managing ingestion, transformations, and reverse ETL as disconnected jobs, teams can now define ordered, repeatable execution across existing Sync components.
The Pipelines feature is designed for common operational analytics workflows, not as a replacement for full orchestration platforms. It gives data teams a way to coordinate what already runs in Sync without adding external dependencies or re-architecting pipelines.
If your team is coordinating multiple sources, transformations, and downstream actions inside Sync, Pipelines reduces friction and makes those workflows easier to understand and operate.
Read the full Pipelines deep dive here.
Iceberg support provides more open-table flexibility
Modern data platforms are increasingly moving toward open-table formats. Open tables decouple how data is stored from how it is queried, giving teams more flexibility, interoperability, and long-term control over their data.
Sync now natively supports writing data into Apache Iceberg tables, alongside existing Delta Lake support. Iceberg enables governed, open tables that can be accessed by cloud data warehouses and lakehouse platforms, without forcing data duplication or proprietary storage layers.
Some teams standardize on Delta, others on Iceberg, and many operate across both. Sync supports these architectures by letting teams decide how data lands, rather than imposing a single table format.
Read more in our dedicated Iceberg blog post.
A new foundation for automation with Sync API 2.0
Sync now has a redesigned API built for consistency, extensibility, and automation. As Sync environments grow, teams increasingly want programmatic ways to manage configuration, trigger execution, and integrate Sync into broader platform workflows. API 2.0 provides a cleaner, more predictable control surface to support those needs.
API 2.0 introduces a consistent resource model with standardized naming, filtering, sorting, and response patterns. This makes it easier to integrate Sync into external systems and internal tooling, and it provides the determinism required for higher-level automation and orchestration scenarios.
This API design also enables Sync to be orchestrated through Model Context Protocol (MCP) servers, like CData’s Connect AI, and user-selected LLMs. In this model, an MCP server exposes Sync capabilities as structured tools, allowing an LLM to create jobs, check status, execute runs, and validate results through real API calls.
Read the API 2.0 overview here.
Supporting deletes in reverse ETL workflows
CData Sync now supports delete operations in reverse ETL workflows, allowing teams to remove records from downstream systems when source data is deleted or no longer meets defined criteria. This ensures that operational systems stay aligned with the current state of analytics and business logic, rather than accumulating stale or orphaned records over time.
By supporting deletes alongside inserts and updates, Sync enables more complete data synchronization scenarios, including lifecycle management for segments, audiences, and operational datasets that change dynamically.
Expanded Change Data Capture for SAP HANA
Sync now supports Change Data Capture (CDC) for SAP HANA, enabling near real-time replication of transactional changes into analytics and operational targets.
SAP systems remain central to many enterprise environments, and keeping downstream systems current has historically required heavy batch processes or legacy tooling. CDC for HANA helps close that gap while fitting into the same replication patterns Sync customers already use across other enterprise databases.
Explore the full release notes and dive deeper into the features above to see how they fit into your environment.
