My Error -- the column delimiter for column ... was not found.

Question

Post reply

My Error -- the column delimiter for column ... was not found.

Mark F-428640

Hall of Fame

Points: 3659
More actions
May 19, 2009 at 9:51 am

#134431

I am attempting to import a text file which is comma delimited and pipe (|) text qualifier I am getting the error the column delimiter for column "Sequence" was not found. This particular field is an integer (incremental field) because of this I changed the field data type to unicode text simular to the other fields thinking this would resolve my issue unfortunately it didn't.
Any suggestions would be greatly appreciated.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Ramesh Saive SSC-Insane Points: 24275 More actions · Answer 1

Can you post some sample data from the file to know how it looks?

--Ramesh

Mark F-428640 Hall of Fame Points: 3659 More actions · Answer 2

|John |,|Doe |,| |,| |,| |,| |,|275 Mystreet |,| |,|MyCity |,|PR|,|Postal|,|Code |,|4|

|Jane |,|Dollar |,| |,| |,| |,| |,|14 Her Street |,| |,|HerCity |,|PR|Postal|,|Code |,|5|

Above is a couple lines of the code with names city replaced

Mark F-428640 Hall of Fame Points: 3659 More actions · Answer 3

Sorry not code data and the last numeric field is the Sequence field being referred to in the error

Phil Parkin SSC Guru Points: 246985 More actions · Answer 4

Please post the error message.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

Tim Mitchell SSCoach Points: 15685 More actions · Answer 5

Is the "Sequence" column the last column you have defined in your flat file connection? If so, you're short by 1 column since you have a trailing pipe at the end.

Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices

Phil Parkin SSC Guru Points: 246985 More actions · Answer 6

Tim Mitchell (5/19/2009)
Is the "Sequence" column the last column you have defined in your flat file connection? If so, you're short by 1 column since you have a trailing pipe at the end.

Pipe is the text qualifier, not field delimiter, so I think it looks OK. Looks more like there is a discrepancy somewhere in data types between integer and string for the final field.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

Tim Mitchell SSCoach Points: 15685 More actions · Answer 7

You're right, I misread the OP's spec. Thanks.

Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices

Ramesh Saive SSC-Insane Points: 24275 More actions · Answer 8

Mark Fyffe (5/19/2009)
|John |,|Doe |,| |,| |,| |,| |,|275 Mystreet |,| |,|MyCity |,|PR|,|Postal|,|Code |,|4|
|Jane |,|Dollar |,| |,| |,| |,| |,|14 Her Street |,| |,|HerCity |,|PR|Postal|,|Code |,|5|
Above is a couple lines of the code with names city replaced

The file format looks okay to me, can you post the exact error message (screen shot if possible)?

--Ramesh

Mark F-428640 Hall of Fame Points: 3659 More actions · Answer 9

Appreciate the responses guys I finally figured it out and feel a little dumb now I have the answer. Apparantly I had exported the file with an extra field and the SSIS package was not liking that. After I exported the file correctly the error vanished and my package ran properly. I guess I should have had two coffees yesterday -- thanks again for all your input.

Mark

Tim Mitchell SSCoach Points: 15685 More actions · Answer 10

Glad it's working, thanks for the update.

Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices

keishahutch Grasshopper Points: 13 More actions · Answer 11

Thank you for sharing!

This just solved my issue.

The client sent a csv file with additional columns that weren't in the other csv files. Essentially, the additional columns are not in our database.