TimeOut on Fabric Pipeline copying Lakehouse table to Fabric Warehouse

[Sureshot]

TimeOut on Fabric Pipeline copying Lakehouse table to Fabric Warehouse:

DWCopyCommandOperationFailed
ErrorCode=DWCopyCommandOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message='DataWarehouse'
Copy Command operation failed with error ''Execution Timeout Expired.
The timeout period elapsed prior to completion of the operation or the server is not responding.'.,
Source=Microsoft.DataTransfer.Connectors.MSSQLImport,''Type=Microsoft.Data.SqlClient.SqlException,Message=Execution Timeout Expired.
The timeout period elapsed prior to completion of the operation or the server is not responding.,
Source=Framework Microsoft SqlClient Data Provider,''Type=System.ComponentModel.Win32Exception,Message=The wait operation timed out,
Source=,'

[Sureshot]

The solution was to not copy the data and instead use shortcuts and data tables in medalion when referencing in Warehouse.

[v-menakakota]

Hi @Sureshot ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-menakakota]

Hi @Sureshot ,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.

Thank you.

[v-menakakota]

Hi @Sureshot ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-menakakota · Accepted solution]

Hi @Sureshot ,

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

Fabric pipelines have execution time limits. You can increase the timeout setting in the Copy activity Go to your Copy activity settings look for Command Timeout in the Destination settings and increase the value .

Also a high batch size can cause timeouts. In the Copy activity settings, reduce the batch size. Try a lower value like 50,000 rows or 100 MB per batch.

If the Lakehouse table is too large, consider filtering data before copying.

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Regards,
Menaka.