Forum Discussion
Copy Activity is Failing while merging the data into SQL DB
Hi SivaReddy24680 ,
Thank you for reaching out to the Microsoft Fabric Community.
Based on your explanation, the data is being read successfully from the HANA source, but the process is failing when trying to write to the SQL table in Microsoft Fabric. The error messages like "Execution Timeout Expired" and "The wait operation timed out" usually happen when the system takes too long to write a large amount of data especially when using operations like merge or upsert.
To fix this, you can try increasing the command timeout setting in your Copy Activity, so the system has more time to finish the write operation. Also, enabling batch writes can help break the data into smaller chunks, which often makes the load more reliable. Another approach is to first load the data into a temporary staging table and then move it into your final table using a stored procedure or notebook. This gives you more control and avoids writing everything in one long operation. It’s also a good idea to check if there are any triggers, indexes, or other activities on the SQL table that might be slowing things down.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Hi SivaReddy24680 ,
Thank you for reaching out to the Microsoft Fabric Community.
Based on your explanation, the data is being read successfully from the HANA source, but the process is failing when trying to write to the SQL table in Microsoft Fabric. The error messages like "Execution Timeout Expired" and "The wait operation timed out" usually happen when the system takes too long to write a large amount of data especially when using operations like merge or upsert.
To fix this, you can try increasing the command timeout setting in your Copy Activity, so the system has more time to finish the write operation. Also, enabling batch writes can help break the data into smaller chunks, which often makes the load more reliable. Another approach is to first load the data into a temporary staging table and then move it into your final table using a stored procedure or notebook. This gives you more control and avoids writing everything in one long operation. It’s also a good idea to check if there are any triggers, indexes, or other activities on the SQL table that might be slowing things down.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Hi SivaReddy24680 ,
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.