Forum Discussion
ADF Copy activity runs for too long
My ADF copy activity takes 4 hours to run and ultimately times out after 2 hours of write time from interim tables.
Source=Mariadb On-prem, Destination=AZURE SQL.
I am running it on Self-Hosted IR on a VM with max disk size.
What can be the possible reasons? How to increase write time on ADF?
1 Reply
Your ADF copy activity is timing out because of slow write throughput to Azure SQL combined with self-hosted IR bottlenecks. Common causes include network latency from on-prem to Azure, insufficient batch size or parallelism, Azure SQL throttling, or interim staging table overhead. You can improve performance by tuning batch size, parallel copy settings, staging options, and IR resources, and by monitoring Azure SQL DTU/CPU usage.
