Skip to content

Commit bd7c64b

Browse files
authored
Merge pull request #94406 from kromerm/dataflow-1
Update data-flow-troubleshoot-guide.md
2 parents 1e66629 + a542689 commit bd7c64b

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

articles/data-factory/data-flow-troubleshoot-guide.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,14 @@ This article explores common troubleshooting methods for data flows in Azure Dat
6363

6464
- **Resolution**: Change the name of the table that you are trying to create
6565

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+
6674
## General troubleshooting guidance
6775

6876
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

Comments
 (0)