When the expression is set on RowDelimiter property on a Flat File Connection Manager, the expression is ignored
For the limitation above, there are two approaches to handle the issue:
1. Copy Data Flow for each Row Delimiter. This takes much effort when we want to upgrade or maintain.
Refer here: http://goelneha.com/ssis-reading-files-with-row-delimiter-identification-at-run-time/
2. Create a new file with standard format. This have two limitations:
- If the file is very large, it takes much time to create new file
- Permission issue on production server
Refer here: http://krishan30.blogspot.com/2013/07/how-to-handle-flat-file-row-delimiter.html
After discuss with team, we decide that we will check row delimiter at run time, if we found row limiter such as {CR} or {LF} only, we will confirm client that this is not the file with row delimiter we support, it should be {CR}{LF}.
0 comments:
Post a Comment