Script Task Carraige Return

Question

Post reply

Script Task Carraige Return

smacumber 77733

Ten Centuries

Points: 1288
More actions
October 19, 2010 at 2:38 pm

#149037

I have a script task that takes XML data and puts it into a text file, works fine.
Problem is when I go to import the text file I get an error
"The last row in the sampled data is incomplete. The column or the row
delimiter may be missing or the text is qualified incorrectly."
I have a Carriage Return and Line Feed in there at the end on its own line
that is causing a problem to import into SQL, how do I get rid of it?
I have to put the Carriage Return and Line Feed in to make new lines so how
do I get rid of this last line?
Thanks!

Viewing 7 posts - 1 through 7 (of 7 total)

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

Phil Parkin SSC Guru Points: 247180 More actions · Answer 1

Modify your script task slightly to not insert the final <CR><LF>? Or is that too obvious?

Koen Verbeeck SSC Guru Points: 259197 More actions · Answer 2

Phil Parkin (10/20/2010)
Modify your script task slightly to not insert the final <CR><LF>? Or is that too obvious?

Relax. The week is almost in the middle. It is almost weekend 🙂

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Phil Parkin SSC Guru Points: 247180 More actions · Answer 3

da-zero (10/20/2010)
Phil Parkin (10/20/2010)
Modify your script task slightly to not insert the final <CR><LF>? Or is that too obvious?
Relax. The week is almost in the middle. It is almost weekend 🙂

🙂 You're right. I'm off to do some yoga.

smacumber 77733 Ten Centuries Points: 1288 More actions · Answer 4

I did, still appears.

Thanks for the obvious, I'm not that new.

Phil Parkin SSC Guru Points: 247180 More actions · Answer 5

Are you saying that your script task does not put the characters there but that something else does?

Koen Verbeeck SSC Guru Points: 259197 More actions · Answer 6

If you really can't get rid of those final characters (because apparently some "inverse-thief" puts them there), you can always try to put some bogus data in there and then get rid of it again with the condition split.

Dirty, but it works.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP