Forum Discussion
Same SQL Source table - ADF Copy Activity Succeeds but Fabric Copy Activity Fails- Auto create table
Hi AJAJ,
Interesting. I wonder if that em-dash is taking up more bytes in the fabric implementation.
If you set the target to be a varchar(25) or 30, does it work then?
If not. I think a ticket with mirosoft would be helpful here. Something is up.
Yes when i manually widended the target table column and it ran fine. Cant be declaring source table structures manually (each table has many columns so even if one column is casted to varchar greater than source, another column creates issue.) copy activity should autodetect especially when source is a SQL server.
Something is a bug. i wish someone from microsoft could take a look. I used trial version and paid version too. Both have same issue. I have worked on Azure copy activity for 5 yrs using various sources. Never came across this issue. i created this fabric pipeline from scratch multipletimes..
95 tables to be processed - lookup and foreach loop thru with appropriate select statement (eg select col1, col2 from tableA and so on) on copy activity.
18 tables are causing similar error.
Verified len of Source SQL server tables and values. Fabric is turning out to be a crapy show here.
Same thing with reading pipedelimited csv files. Some files are fine but are having issues with copy activity while sames files runs smoothly in ADF.
Hi AJAJ,
I recommend you open a ticket with Microsoft.
Automatic mapping tools have come a long way, but they are not 100% reliable yet.
What you can do is in the source query, you can write a select statement that will cast the columns to a larger datatype, and then the copy data activity mapping will pick it up.
As tayloramy suggested to raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
