MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
SqlParallelFailedToDetectPartitionColumn

What does this error mean?

ADF could not detect a partition column for parallel copy from a SQL source. Parallel copy requires a numeric or datetime column to partition data into ranges.

Common causes

  • 1The SQL source table has no suitable numeric or datetime column that ADF can use for range partitioning
  • 2Auto-detect was selected but the table does not have a primary key or a column that meets partitioning criteria

How to fix it

  1. 1Specify the partition column explicitly in the copy activity source settings instead of relying on auto-detection.
  2. 2Choose a numeric or datetime column with good cardinality (e.g., an ID or created_date column) as the partition column.
  3. 3Set the partition upper bound and lower bound values to match the actual data range in the selected column.
  4. 4If the table has no suitable partition column, disable parallel copy and use sequential copy instead.

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

Other data source errors