What causes SqlBatchWriteTransactionFailed?

A row in the batch violates a primary key, unique, or foreign key constraint. A null value in the batch was inserted into a NOT NULL column. A deadlock occurred on the destination table during the batch write. The transaction log of the SQL database filled up during the batch write

How do I fix SqlBatchWriteTransactionFailed?

Check the ADF activity run error for the specific SQL error code within the transaction failure.. Enable fault tolerance on the copy activity to skip failed rows and log them to storage for investigation.. Review the source data for constraint violations before the copy — deduplicate on key columns.. If a deadlock: add a retry policy with exponential backoff to the copy activity.. Monitor SQL transaction log usage and grow the log file or enable auto-growth if needed.

High severitydata source

Power BI Refresh Error:
SqlBatchWriteTransactionFailed

What does this error mean?

An ADF copy activity batch write to SQL Server failed and the transaction was rolled back — any constraint violation or transaction error rejects the entire batch.

Common causes

1A row in the batch violates a primary key, unique, or foreign key constraint
2A null value in the batch was inserted into a NOT NULL column
3A deadlock occurred on the destination table during the batch write
4The transaction log of the SQL database filled up during the batch write

How to fix it

1Check the ADF activity run error for the specific SQL error code within the transaction failure.
2Enable fault tolerance on the copy activity to skip failed rows and log them to storage for investigation.
3Review the source data for constraint violations before the copy — deduplicate on key columns.
4If a deadlock: add a retry policy with exponential backoff to the copy activity.
5Monitor SQL transaction log usage and grow the log file or enable auto-growth if needed.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-synapse-sql