JJ of Eugene OR
2006-05-15 20:38:02 UTC
SSIS Community:
I have some .txt files I need to work with in SSIS. When I create a Flat
File connection, the connection manager does not seem to recognize the row
delimiters. For example, in a file that contains two rows, all I see in the
preview pane is one long row, as if the connection manager doesn't see the
carriage return/line feed at the end. Instead, the preview pane (and columns
pane) shows two black boxes in place of each of the row delimiters.
Some things to note:
1) I can look at the exact same files in DTS, and DTS reads the file
perfectly. In other words, my DTS package sees the row delimiters just fine.
2) I have created other flat file connections in other SSIS packages
without problem. One difference between flat files which have worked and
flat files which have not is that the problem files were generated by a
mainframe. The files that have worked OK were generated from an MS
Access/Jet file. (I don't have control over this. I'm just hoping that
knowing that the files were generated by a mainframe might trigger an idea
for someone.)
Why would DTS get it right and not SSIS? What can I do to get SSIS to work
right?
All help much appreciated!
- JJ
I have some .txt files I need to work with in SSIS. When I create a Flat
File connection, the connection manager does not seem to recognize the row
delimiters. For example, in a file that contains two rows, all I see in the
preview pane is one long row, as if the connection manager doesn't see the
carriage return/line feed at the end. Instead, the preview pane (and columns
pane) shows two black boxes in place of each of the row delimiters.
Some things to note:
1) I can look at the exact same files in DTS, and DTS reads the file
perfectly. In other words, my DTS package sees the row delimiters just fine.
2) I have created other flat file connections in other SSIS packages
without problem. One difference between flat files which have worked and
flat files which have not is that the problem files were generated by a
mainframe. The files that have worked OK were generated from an MS
Access/Jet file. (I don't have control over this. I'm just hoping that
knowing that the files were generated by a mainframe might trigger an idea
for someone.)
Why would DTS get it right and not SSIS? What can I do to get SSIS to work
right?
All help much appreciated!
- JJ