Forum Discussion
Same SQL Source table - ADF Copy Activity Succeeds but Fabric Copy Activity Fails- Auto create table
Hi AJAJ,
Azure Data Factory may just truncate the data without throwing an error. Fabric Data Factory does not, it will fail instead of allowing the data to truncate.
Interesting. I dont have access to source at this point and working on getting access.
When source is SQL Server and has table structure as varchar(100), will fabric pick up same column as with shorter length? and assign varchar(20) while source has 100? so data is coming with more length? (i understand if its other platform, copy activity may assign varchar(max) source SQL server is microsofts own product) And i dont think currently successfully running ADF is truncating data. Never came across data truncation in past 5+yrs of work in azure adf copy activity. Its weird since ADF copy activity and fabric copy activity point to the same source table. Few tables have the same error while its running fine on ADF Copy activity.
At this point im waiting to get access to source to compare.
- tayloramy7 months agoSuper User
Hi AJAJ,
In my experience, Fabnric is pretty good at auto determining the size of columns from SQL Server. I have seen problems when Fabric is selecting from a view, both on SQL Server and Oracle, but with a table I have never had these problems.
What does your set up look like?