Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chilluk
Starting Member
24 Posts |
 Posted - 2007-06-06 : 10:27:11
|
| I am migrating from 2000 to 2005 and in the process of rewriting DTS to SSIS. So far so good.I have an import of a flat file that I need to reproduce that works fine in DTS but throws SSIS.The file contains details of products, and has a Long Description field that may contain lots of different chars - CR & LF amongst them. It's source and destination columns are Text type.The file is tab delimited, text delimited with double quotes, with row delimiters of CRLF and column names on row 1.The error SSIS throws is "The column delimiter for column "LongDescription" was not found"I imagine (perhaps wrongly) that this is because of the extra CRLFs but it worked fine in DTS. It also previews fine, and lets me define the column properties OK in SSIS package designer.Any help greatly appreciated. I am trying to avoid the obvious thing of replacing those chars in that field at this point as currently the export is shared between a live production server, and my test 2005 rig.Thanks v much.Chris. |
|
|
chilluk
Starting Member
24 Posts |
Posted - 2007-06-07 : 10:40:09
|
| OK I decided to work round it - so instead I have replaced crlf with obscure characters, and even used obscure characters as my column/text delimiters - anything else and SSIS was baulking at the file. Seemed to do the trick.Now though out of 52,000+ I am getting an import of around 38,000 records.No errors reported or raised - I have even tried redirecting error rows into another flat file.Please help as now tearing hair out!! |
 |
|
|
|
|
|
Importing Carriage Returns - Now LOST DATA