Truncation error with MS SQL Bulk Load snap, column reported not issue, which column is real issue?
We're occasionally getting a frustrating truncation error using MS SQL Bulk Load snap. The error 'column' reported is -not- the issue, so which column is causing issue?? Error details below. I can isolate the incoming record from the incoming csv file (Row 74740 in this case) , the record/doc has many fields and the reported column (Column 13 in this case) is -NOT- where the data truncation error is happening. Is there a way I can pin point the actually field/column which the trunc error is happening? I suspect the fields are being re-ordered in some manner to feed to the bcp command for the snap. Is there a way to see the -actual- bcp cmd text the snap is passing to bcp for execution? The 'Column 13' reported in this error is not helpful in debugging the pipeline when it fails with these data truncation errors. MUCH THANKS for any assistance or insights! Error below: Failed loading record Resolution: Please address the reported issue. Reason: #@ Row 74740, Column 13: String data, right truncation @# w
