Operation on target Copy data1 failed: Failure happened on 'Source' side. ErrorCode=UserErrorFailedFileOperation,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The file operation is failed, upload file failed at path: 'smartboo

Aman Pahariya 20 Reputation points
2024-05-27T04:36:23.3833333+00:00

While running a pipeline from SQL Server table data to Azure Blob Storage, I am facing the mentioned error.

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

1 answer

Sort by: Most helpful
  1. AnnuKumari-MSFT 31,731 Reputation points Microsoft Employee
    2024-05-28T07:37:55.67+00:00

    Hi Aman Pahariya ,

    Welcome to Microsoft Q&A platform and thanks for posting your query here.

    It seems the issue is due to the fact that the data space reached the maximum data size limit, kindly try the below mitigation options suggestion in the official document:

    • Increase maximum data size of the database or elastic pool, or scale up to a service objective with a higher maximum data size limit. See Scale single database resources and Scale elastic pool resources.
    • If the database is in an elastic pool, then alternatively the database can be moved outside of the pool, so that its storage space isn't shared with other databases.
    • Shrink a database to reclaim unused space. In elastic pools, shrinking a database provides more storage for other databases in the pool. For more information, see Manage file space in Azure SQL Database.
    • Check if high space utilization is due to a spike in the size of Persistent Version Store (PVS). PVS is a part of each database, and is used to implement Accelerated Database Recovery. To determine current PVS size, see PVS troubleshooting. A common reason for large PVS size is a transaction that is open for a long time (hours), preventing cleanup of row older versions in PVS.
    • For databases and elastic pools in Premium and Business Critical service tiers that consume large amounts of storage, you might receive an out-of-space error even though used space in the database or elastic pool is below its maximum data size limit. This can happen if tempdb or transaction log files consume a large amount of storage toward the maximum local storage limit. Fail over the database or elastic pool to reset tempdb to its initial smaller size, or shrink transaction log to reduce local storage consumption.

    Additionally, kindly consider checking the troubleshooting document here: Resolve tempdb-related errors and exceptions in Azure SQL Database

    Hope it helps. Kindly accept the answer by clicking on Accept answer button. Thankyou

    0 comments No comments