June 25, 2014 at 4:02 pm
This may not be 100% the answer, but different parsers by default may use different line terminators (CR or LF). Generally when both are used it means whichever the parser is configured to use as the line terminator is more than likely one of the two.
If it's causing problems for you to parse them, I'd open the file in your favorite text editor (assuming it's not too big) and use a regular expression to replace the line terminating "LF" to "CRLF", although SSIS should also give you tools to change what line terminator it expects.
June 25, 2014 at 4:15 pm
I need to see the sourcing code or specifics about the technique the originator is using Michael to really nail down why that's happening.
Jay's recommendation above is your best bet for a fast fix to a one off.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
June 26, 2014 at 2:49 am
Thanks for this. I will use the find replace for now. I thought it may be a setting in windows or SSMS which could be changed. Hopefully the final regular export does not have the issue.
I could set SSIS to change the expected delimiter but I would like to reuse an existing package to import data from multiple source files.
Thanks again!
June 26, 2014 at 8:25 am
Just an update on this. I have figured out what the problem is. We are using an FTP to move the files from one location to another. Turns out the FTP is replacing the CRLF with a LF.
Doh:doze:
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply