Copy Data Activity when used with Linked Service version 2.0 is very very slow compared to 1.0

Question

We are using Azure Data Factory --> Copy Data Activity to copy data from Oracle Database to ADLS.

When we are using Linked Service with Version 1.0, the Copy is working fine with speed around 10 MB/sec.

However when we are using Linked Service with Version 2.0, the Copy is working very slow with speed around 60 KB/sec.

Please let us know how Linked Service can be fixed to work speed with Version 2.0 .

Answer 1

Hello Immaneni, Nanda,

Thank you for posting your question in the Microsoft Q&A forum. 

The performance degradation when using Oracle Linked Service v2.0 in Azure Data Factory (ADF) likely stems from configuration differences between the legacy v1.0 and newer v2.0 connectors. Here’s how to diagnose and resolve the issue: 

You may try below configurations if not tried already:

1. Driver/Protocol Settings: V2.0 defaults to Thin JDBC driver, which may be slower than v1.0’s OCI driver. Explicitly set oracleDriverType to "OCI" in the linked service JSON. 
2. Fetch Size Optimization: V2.0 might use a smaller fetch size. Add fetchSize parameter (e.g., 10000) to reduce round trips. 
3. Parallel Copies: Ensure parallelCopies is enabled in the Copy Activity (default is serial in v2.0). Set to 10–20 for large datasets. 
4. Network/Proxy Issues: V2.0 may route traffic differently. Check if firewalls/proxies throttle connections (compare NSG rules between tests). 

Few validation Steps as below:

• Test with OCI driver + adjusted fetch size. 
• Monitor performance via ADF Monitoring Hub to identify bottlenecks. 

Reference Microsoft documentation link - https://learn.microsoft.com/en-us/azure/data-factory/connector-oracle?tabs=data-factory#performance-optimization  

If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.