Todd Engen (8/25/2008)
One of the workarounds is to read an entire line is as a single row, then use the Script Component and write your own logic to break it apart and output.
Yes, this has been Microsoft's response for most of the last 10 years on this: either pre-process it or post-process it. Both of which call into question the value of an automated import processor in the first place. After all, this is the most common export/import format ever and if they cannot process it without additional coding, why bother with this automated tool in the first place?
Now I just write my own import routines. It may not run as fast as some SSIS/DTS packages, but it saves me many weeks of time & effort.
Vote on it over at Microsoft Conect, maybe they'll fix it; It's still broken in SSIS in SQL 2008.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=312164
Thanks for the pointer Todd, I will.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]