CData Sync

Hey All, I’d like to enable cdata sync’s alter schema feature. However, I want to set any newly discovered columns  in the source table to a string data type in the target table. I’d also like to Alter schema to not change the data type of the target table, even if the source data type changes. My staging tables all use string data types for every field. Is this possible? is there an advanced setting that I can enable?  I checked the cdata sync documentation for Alter Schema and didn’t see this mentioned. 

I'm using CData Sync with a SQL Server source in a Standard job (incremental check column, no CDC or CT enabled). If a new column is added to a source table, will Sync automatically detect and add it to the destination on the next run? The Features page says schema changes are detected "in every run", but the SQL Server Source page only describes this behavior under CT/CDC. Does it work without CT/CDC enabled?

We’re currently testing the S3 destination for various sources using CSV file format and would like to be able to do 2 things:Specify a subfolder per job or task Append the table name to the destination filefor example, if the S3 Connection is setup to a folder cdata/ i would like to be able to output the following structurecdata/ salesforce/ account/ account_20260722113426039_1.csv account_20260722113426039_2.csv contact/ contact_20260722113426039_1.csv servicenow/ task/ task_20260722113426039_1.csv ..etcThe closest I’ve been able to get is appending something to the table/folder name, and I can’t find any usable option to control the file name format. I’ve tried changing the batch naming convention in the connection settings but it had no affect.cdata salesforce_account 20260722113426039_1.csv 20260722113426039_2.csv ..etc Additionally - Ther’es no documentation on the “Advanced” features of the S3 destination other than “you probably won’t need it” --

Is there a way to introduce a delay between steps in a CData Sync Pipeline? We have a limitation from a source API and need to ensure we delay our API requests by 15 seconds between calls, hence looking to add this delay.

We have been testing with the new pipelines but we ran into an issueA pipeline got canceled and now its stuck on canceling status.Its now impossible to start or delete or the pipeline.We can remove items out of the pipeline and even with everything removed it is still stuck on canceling (but all items are removed.)Even stopping the CData Sync service (and rebooting the server) is not stopping the canceling status.is there a way to stop and remove this pipeline?

We upgraded to the latest version of the CDATA last weekend. After that tasks that use environment variables for the ReplicateStartDate property are currently failing.  Current Configuration Pre job event <api:set attr="out.env:currenttimestampminus36months"  value="[null | now() | dateadd('month', '-36', 'yyyy-MM-dd')]" /><api:push item="out" /> Query:  REPLICATE [CTL].[AccountHistory] WITH ReplicateStartDate = '{env:currenttimestampminus36months}', ReplicateInterval = '1', ReplicateIntervalUnit = 'Months', DeletionBehavior = 'SkipDelete', DropTable = 'false' SELECT * FROM [AccountHistory] Error:[0] '{env:currenttimestampminus36months}' is not a valid value for the ReplicateStartDate property. We expect a date (yyyy-MM-dd) or an int.  Attempted Fix Pre job event :<api:set attr="out.env:currenttimestampminus36monthsModified"  value="[null | now() | todate('yyyy-MM-dd', dateadd('month', '-36', 'yyyy-MM-dd'))]" /><api:push item="out" /> Query:  REPLICATE [CTL].[Ac

We are experiencing inconsistent delete replication behavior when syncing a very small and stable ServiceNow table (≈10 rows) into SQL Server using CData Sync v26.Despite following all recommended configurations and upgrading both Sync and the ServiceNow driver, record deletions in ServiceNow are occasionally not detected by CData Sync, resulting in extra rows remaining in the SQL destination.This has caused incorrect data to appear in executive-level dashboards, impacting trust in reporting. Observed BehaviorRecords are deleted in ServiceNow No incremental sync runs successfully with no errors The deleted records remain in SQL Server Dashboard shows more rows than exist in ServiceNow Manual SQL cleanup is required to restore accuracyExample:Source (ServiceNow): 8 rows Target (SQL): 10 rows The extra 2 records no longer exist in ServiceNowExpected BehaviorDeleted records in ServiceNow should be reliably removed in SQL Sync behavior should be consistent regardless of table sizeWhat We H

In CData Sync API connector with Bearer token authentication, currently it's not possible to provide and configure an endpoint from which a new token can be acquired. What are the other possible ways then to update the token dynamically then? This thread discusses a solution in CData Arc but I am not sure if that will be applicable here in CData Sync.This another thread discusses adding a manual bearer token in custom header for CData Sync, but how can the token value be updated dynamically?Is it possible to acquire the token in the Pre-Job event and then set it as an environment variable? Are environment variables (set up in the Pre-Job event) accessible in the Connection configuration?

A new year brings new capabilities! We’re excited to kick off 2026 with one of our largest CData Sync releases yet, this Q1 roll out is packed with enhancements designed to give you more flexibility, control, and power across your data pipelines. Here’s what’s new in Sync Q1 2026: ❄️ Apache Iceberg Destination Support CData Sync now supports the Iceberg file format and catalog, enabling modern lakehouse architectures with open, reliable table formats. Iceberg destinations are now available for:  Amazon S3  Azure Blob Storage  Azure Data Lake Storage  Google Cloud Storage  🚦 Visual Pipelines in the UI We’re excited to preview Pipelines, an upcoming point-and-click UI experience for managing job and event dependencies in Sync. Pipelines will make it easier than ever to orchestrate and visualize Sync workflows.🔄 CDC Catalog Enhancements: SAP HANA We’ve expanded our CDC catalog with Enhanced CDC (ECDC) support for SAP HANA, making it easier to capture and replicate changes from one of

Hi,I’m trying to use Sync to replicate data from Salesforce into a Postgres database.  I have a full load working, and every night it truncates then reloads the tables.I’m having a lot of problems setting up another job that then runs an incremental update periodically.  It seems straightforward to set up.  My jobs incremental settings are:Start Date:  2026-01-06 Replication Interval : 1 dayWhen I run the job, I consistently get the same error, regardless of which Salesforce object I try to incrementally update.  In this case my source is Building__c, and the destination is the Postgres table salesforce.building. The error I get is:  [0] Updating Row is failed. ERROR: Server error [SQL state: 42P01]: relation "salesforce_building__r_1329269084" does not exist (Character 13) , AffectedCount: 0I can’t find any mention of this type problem in the documentation, and have followed all the steps in the docs to set this up.Has anyone else encountered something like this, or perhaps have an id

When configuring a replication Job after creating a Connection to your SQL Server database, you may initially find that you are unable to utilize this Connection as a Destination.The Connection appears as intended when selecting a Source for the Job:However, the same Connection does not appear when selecting a Destination:What can be done to resolve this?

The CData Sync clustering feature allows multiple Sync installations to operate together as a single, scalable, and highly available environment. By distributing workloads across multiple nodes, clustering ensures continuous operation, automatic failover, and consistent performance even as data movement needs grow.In this article, you’ll learn how to: Set up Sync nodes to share a unified application directory Configure a shared application database for consistent metadata and job management Enable and activate Cluster Mode across all Sync installations Ensure reliable, distributed job execution with automatic node balancing To learn more, read: Configuring Clustering for CData Sync

Working with PostgreSQL data that includes “Infinity” values? Learn how to manage and sync these special values effortlessly using CData Sync. Our newest guide walks you through the necessary steps and best practices to keep your data clean and reliable.Full guide: https://www.cdata.com/kb/articles/sync-postgresql-infinity-values.rst

Hey CData Community!Microsoft’s SQL Server 2025 brings AI into the heart of the database with new native vector support, enabling you to store, search, and analyze embeddings directly inside SQL Server. When paired with CData Sync, you can easily connect and replicate data from 250+ sources to power AI workflows like semantic search, RAG pipelines, and anomaly detection — all within SQL Server.Check out the full guide here: https://www.cdata.com/kb/articles/sync-sqlserver25-ai-workflows.rst

Fall is here and so is CData Sync’s Q3 2025 release! Our latest updates are designed to help you unlock more value from your data, faster and more efficiently. ⚡ Enhanced CDC Catalog Expansion: You asked, we delivered Sync now supports DB2 protocol AS400/iSeries and MySQL for even broader data replication capabilities! 🔄 Reverse ETL Catalog Expansion: New destinations now supported, including Salesforce Pardot, Salesforce Marketing Cloud, Sage Intacct, and Veeva Vault to enhance your reverse ETL capabilities ✨ Open Delta Table Support: Now available for all your favorite data lake destinations such as: Amazon S3, Azure Blob Storage, Google Cloud Storage, and Azure Data Lake Storage powering your delta integrations across Databricks, Fabric, and more! ⚡ Faster File Replication: CSV, Avro, Parquet, and One Lake Mirroring are now 90% faster for smoother large-workload handling. 🛠 Generic JDBC Connector: Unlock source-only connectivity and schema discovery for databases beyond officially

Most ETL/ELT tools provide connectivity to Workday; however, the connection is limited because it is only through Reports as a Service (RaaS). With the CData Sync Workday connector, users get more connection options, including support for:Prism Data Catalog Workday Query Language (WQL) RaaS REST API SOAP APIOur latest article reviews how the Workday connector for CData Sync delivers full connectivity when compared to other ETL/ELT tools' connectors.Read the full article: https://www.cdata.com/kb/articles/workday-sync.rst

We’re excited to share the latest updates in CData Sync, now live with powerful new features designed to elevate your data integration experience: 🔁 Microsoft Mirroring as a Destination In partnership with Microsoft, Sync now supports OneLake Mirroring, enabling direct ingestion into the Microsoft Fabric ecosystem. With native Parquet support and catalog integration, it's a seamless way to accelerate your lakehouse strategy. 📈 CDC for SAP ERP Deliver near real-time replication from SAP ERP systems using RFC, expanding our enterprise-grade CDC coverage. 🔐 Stronger Identity & Access Management Enjoy a smoother, more secure experience with revamped SAML integration and 2FA 🌟 Coming in July!  New Reverse ETL Destinations: Pardot, Sage Intacct, and Salesforce Marketing Cloud  Open Table Format Support: support for DeltaLake on AWS, Azure, and GCP.  📚 View full release details in the Current Release Documentation. 🆓 Start a Free Trial or upgrade your Sync install to explore the la

Hey CData Community!Looking to bring your Salesforce data into SAP Datasphere without the headaches? Our latest post, Replicate Salesforce Data to SAP Datasphere with CData Sync, walks you through the full setup — from database user creation to job execution — so you can get your external data flowing into Spaces fast.No native connector? No problem. With CData Sync, you can plug in Salesforce (or any of 270+ sources) and start building with real-time, reliable data. Check out the full guide here: https://www.cdata.com/kb/articles/sync-sap-datasphere.rst

Hey CData Community!Manually enabling Change Tracking for every Dynamics 365 entity? That is a lot of effort.Good news. CData Sync can do it for you using a stored procedure.It automatically enables Change Tracking for the right entities so you can set up incremental replication without the manual work.Want to see how it’s done? Check it out here: https://www.cdata.com/kb/articles/dynamics365-change-tracking.rst

Hey CData Community!Just dropped: a quick deep-dive on the new Enhanced CDC feature in CData Sync• 9× faster replication (10 k changes: 6 s vs 54 s)• Always-on log reading + staging area = reduced wait at run time• Step-by-step setup, benchmarks, and diagrams inside Refer to the following link to read the post: https://www.cdata.com/kb/articles/sync-enhanced-cdc-performance.rst

Hi,I have 3 years worth of data. All the data stay the same but the latest 3 months are dynamic. I need to replace the old data with the latest data. But if I do “Drop Table”, it drops all the data and bring all 3 years worth of data and sometimes the system dont seem to be able to handle it.  I would like to keep everything and just have the last 3 months tables dropped and replaced. I dont want the system to have to bring ALL data from the past 3 years. I just need the last 3 months dropped and replaced.  What setup should I do?

Hey CData Community!Moving large volumes of data into Snowflake just got a major performance upgrade. With the release of CData Sync version 24.3, high-volume data replication is now significantly faster and more efficient, cutting job completion times nearly in half for optimized processes.In our recent article, we looked at the enhancements made to CData Sync’s processing engine and explored how these improvements play out across datasets ranging from 1 million to 10 million records.Learn More: https://www.cdata.com/kb/articles/sync-snowflake-performance.rst

Hi,I have Sync version 24.3.9120.0 and I’m using Apache Kafka as source. It’s working fine, except little irritation. When I run task it will replicate only first 150 000 rows and stops after that. Next time I run the task, it replicates 179 000 rows and so on. Row count will increase. Seem to be randomI can run job multiple times and it will continue where it was stopped earlier. Is there way to change this behavior, so that all rows will be replicated at once?