A Flat File Source and Connection Manager step through the rows in a text file and upload them to a SQL Server table. Each row has maybe 20 tab-delimited fields and the CR character (x0A) is used as the row delimiter.
This generally works as expected, but sometimes an additional, unexpected CR character is encountered at the end of a field in the middle of a row and that row is then broken in half at that location so that this single row is turned into two short rows.
When the Data Flow process reaches the short row, it just churns endlessly. It does not write either short row out to either of the Error Output; it just sits there at the bad row until I have to manually kill the operation.
What can I change in order to force the Data Flow Process to write the bad row out to an Error Output and move on to continue processing the file?
HomeCookN