Pipeline Copy Data Activity Timing Out

Ashley Sturgeon 0 Reputation points
2025-05-06T13:08:56.6133333+00:00

I have an ODBC copy data activity that is erroring and the suggestion is to just retry. the table is not the biggest table, and bigger tables successfully copy over.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,486 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Smaran Thoomu 23,095 Reputation points Microsoft External Staff Moderator
    2025-05-06T13:38:36.66+00:00

    Hi @Ashley Sturgeon
    It sounds like you're having trouble with a copy data activity timing out, especially since you mentioned that the table you're working with isn't particularly large, while larger tables copy without any issues. Here are a few things you can try to troubleshoot the problem:

    1. Check for Throttling: It's possible that the source data store is experiencing high utilization or throttling. Check if there are any throttling errors reported. If so, you might want to reduce workloads on the data source or speak with your data store administrator about increasing the throttling limit.
    2. Review Copy Source and Sink Patterns: Make sure that your copy activity isn't running into issues with partitioning. If your source or sink supports partitioning, consider adjusting your parallel copy options. Too many parallel copies might negatively affect performance.
    3. Splitting Data: If the data you're copying is still large relative to your pipeline's settings, consider breaking it down into smaller chunks. You could use a combination of Lookup/ForEach activities to handle smaller datasets concurrently.
    4. Check Network Configurations: If you are utilizing a self-hosted integration runtime, ensure that it’s properly configured and has enough resources to handle the data transfer.
    5. Monitor for Issues: Keep an eye on the application for any warnings or errors during the execution of the pipeline. They can provide further insights into what's going wrong.

    If these steps don't resolve the issue, here are a few follow-up questions that could help clarify things further:

    1. What specific error message are you encountering when the copy activity times out?
    2. How are you currently configuring your copy activity (e.g., data partition options, integration runtime type)?
    3. Have you noticed any patterns in when the timeouts occur, such as specific times of day or under certain load conditions?
    4. Are there any additional transformations or processes occurring in the pipeline that might affect performance?

    Hope this helps! If you have more details, feel free to share!


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.