I originally posted this on microsoft.public.sqlserver.integrationsvcs but have received no response and now after seeing only 133 posts the entire year.... I think nobody actually uses that forum....
I created several very simple flat file (csv) import packages. For the most
part they seem to work fine. Except for one of them (actually two since a
second one is now broken).
The daily files I am trying to import are comma delimited with the first row
containing the headers. The header delimiter is set to {CR}{LF} with the
text delimiter set to double quotes.
For two days (I just wrote the package's yesterday) on one package and for
today's run on the second package, I received the same error of "Error:
0xC0202055 at Import Data, File Source[16]: The column delimiter for column
"xxxxxxx" was not found". The column specified in both errors references
the LAST column which means that it cannot find the header delimiter.
Since the second package worked yesterday but not today, and the only
changed factor is the new source file from today, it makes me think that the
problem is with the source file. Problem is that the file looks fine. I even
loaded both files (yesterday and today) into a hex editor and confirmed
that the header is EXACTLY the same... all the way to the "0D 0A" indicating
{CR} {LF}. (On a side note, the source csv files for the package that failed
both days match and also contain the "0D 0A" values.)
Any ideas?
Thanks,
Jason
One idea is to use the Error Output on the Flat File source and set it to redirect rows. Hopefully, redirected rows will give you a clue of where to look for the missing delimiter.
HTH.
No comments:
Post a Comment