ADF copy actvity fails with errorcode=usererrorsqldwcopycommanderror

Anonymous
2023-06-13T19:28:26.8733333+00:00

Hello,

When running a copy activity in ADF, it fails with the following error:

ErrorCode=userErrorSqlDWCopyCommaderror. Column"couty"not found in SQ DW table.

The issue is with a Copy activity from ADLS to Synapse Analytics failing in the LATAM ADF. This exact same pipeline, is working as expected on the NA Prod ADF This is a parameterized pipeline that’s calling the old pipeline that has been working before

This pipeline only fails when running in a new ADF, when running in the old ADF whwre it was creted, it runs fine.

The new ADF and the pipeline on it were manually created.

Any ideas on this?

Thanks in advance

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,373 questions
{count} votes

1 answer

Sort by: Most helpful
  1. QuantumCache 20,366 Reputation points Moderator
    2023-06-14T16:28:47.0533333+00:00

    Hello @Salomon Henriquez,

    Are you sure the Column 'Couty' exists in the source ADLS table?
    Try running the copy activity in debug mode to see if you can identify the source of the error/

    1. Typo in column name: Make sure that the column name is spelled correctly in both the source and destination datasets. It's possible that there is a typo in the column name in one of the datasets.
    2. Column not present in destination table: Make sure that the column is present in the destination table in Synapse Analytics. It's possible that the column was removed from the table or renamed.
    3. Case sensitivity: Check if the column name is case-sensitive. If the column name is in uppercase in the source dataset and in lowercase in the destination dataset, it may cause the error.
    4. Data type mismatch: Check if the data type of the column in the source dataset matches the data type of the column in the destination dataset. If there is a data type mismatch, it may cause the error.
    5. Permissions: Check if the account used to run the pipeline has the necessary permissions to access the Synapse Analytics table.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.