Skip to main content

Hey All, 

I’m using cdata sync , version  Cross-Platform Edition - 24.2.9064.0. 

I’d like to pull cdata sync’s job history  metadata   into a table in SQL Server, so I can perform analysis. Any suggestions on how to do this? I didn’t find anything in the documentation other than info on how to use the cdata sync GUI, but that is not useful.

I’d even settle for exporting job history data into a .csv file if that is possible. 

Ultimately, I want to be able to perform aggregations on the number of records loaded per job. This can’ tbe done through the existing GUI. 

Thanks! 

Hi ​@Marcus_S 

To answer your question, there are two approaches you can follow to get the requested details on the jobs history:

1) CData Sync provides a REST API that allows you to query configured connections, jobs, and job history. For more details, refer to the documentation:
https://cdn.cdata.com/help/ASM/sync/REST-API.html

2) The other approach consists in accessing the Sync backend databases. Since Sync uses an embedded Derby database, you can connect directly through the file system by specifying the path to the cdata_sync folder within the application directory ("C:\ProgramData\CData\sync\db\cdata_sync" by default). No username, password, or port is required to connect.

You can access it using a database tool like DBeaver. This database contains multiple tables storing information about tasks, jobs, connections, settings, job history, and more. Some key tables include:

sync_connections – Stores configured connections
sync_jobs – Contains job definitions
sync_task – Stores task-related details
sync_job_history – Tracks job execution history
sync_settings – Stores Sync application settings

 

Additionally, if you want to have those data in a SQL Server database, one way to accomplish this would be to follow the instructions below in order to migrate the application database from Derby DB to SQL Server:

https://community.cdata.com/cdata-sync-47/migrating-the-application-database-to-sql-server-914

Feel free to reach out and let us know if you have any questions.


I ended using the Rest API. Previously, I had accomplished this by using a Cdata Sync connection to the SQL Lite Database sitting on the file system. After updating cdata sync, the product had switched to a Derby DB. 

The rest API was the easiest method. Thanks again!