Forum Discussion
Same SQL Source table - ADF Copy Activity Succeeds but Fabric Copy Activity Fails- Auto create table
tayloramy Thanks Taylor. Like i said, same identical pipeline is running fine in existing ADF (same source, same table, same everything) but few tables is not working in fabric. Nothing hardcoded in column mapping. multiple tables get processed by 1 pipeline. Fabric has processed other tables successfully. Data values are not exceeding.
The error is not correct. What i mean is if you connec the same table via ADF it runs fine but not in fabric. no mapping since many tables are processed by 1 pipeline. am i missing anything?
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.