You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/data-flow-troubleshoot-guide.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,6 +63,14 @@ This article explores common troubleshooting methods for data flows in Azure Dat
63
63
64
64
-**Resolution**: Change the name of the table that you are trying to create
65
65
66
+
### Error message: DF-SYS-01: com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated.
67
+
68
+
-**Symptoms**: When writing data to a SQL sink, your data flow fails on pipeline execution with possible truncation error.
69
+
70
+
-**Cause**: A field from your data flow maps to a column in your SQL database is not wide enough to store the value, causing the SQL driver to throw this error
71
+
72
+
-**Resolution**: You can reduce the length of the data for string columns using ```left()``` in a Derived Column or implement the ["error row" pattern.](how-to-data-flow-error-rows.md)
73
+
66
74
## General troubleshooting guidance
67
75
68
76
1. Check the status of your dataset connections. In each Source and Sink transformation, visit the Linked Service for each dataset that you are using and test connections.
0 commit comments