Connector Improvement: Performance Optimization for Azure DevOps Connector Sync
AnsweredWe are experiencing significant performance issues with the Azure DevOps connector due to the volume of historical records in our instance. Currently, a full sync can take 12 hours or more, which severely limits our ability to capture daily, or more frequent, snapshots of data for reporting and analysis.
We are requesting an enhancement to the connector that would allow for incremental syncing, where previously synced rows are retained and only new or updated records are retrieved during each sync. This would reduce the volume of data processed during each run, significantly improving sync times while preserving access to historical data.
Desired Capabilities:
- Ability to configure the connector to sync only new or modified records since the last successful sync OR based on number of days since a row was changed.
- Retention of previously synced data to avoid unnecessary reprocessing.
- Optional additional filters to further limit sync scope may be "nice to have" (e.g., by date range, project, or work item type).
This improvement would enable more efficient data operations and support our need for timely insights from Azure DevOps.
-
Official comment
Hi Scott,
Thank you for raising this improvement request.
We recently updated the high-volume WORK_ITEM and WORK_ITEM_RELATION tables by adding incremental sync and introducing new related tables to improve performance (see changelog: https://fivetran.com/docs/connectors/applications/azure-devops/changelog#october2025).
We also have an additional performance improvement currently rolling out. I see you’ve already opened a support ticket. I’ll ask our support team to include your connection in the early rollout so you can benefit from the improved incremental sync performance sooner.
Thank You,
Vsihal
Please sign in to leave a comment.
Comments
1 comment