June 15, 2011 at 8:43 am
i have a SSIS package (sql 2008), it loads data from a csv file to table. when I run the package, i got 39 rows in the table.
after I promo the package to a SSIS server, I create a job which calling this package. when the job finish, i only see 38 rows in the table.
i checked the csv file, the row missed is the very last row of the file.
what could be the reason?
btw, SSIS is really sucks, much worse than DTS.
_______________________________________________________________
June 15, 2011 at 9:29 am
i found the same issue on MSDN, seems 'a file that sometimes contains an extra CRLF at the end of the file' cause the problem.
but not solution yet, last post at May 24, 2011.
i really don't want to turn a simple data transfer task to a script task! pls help.
Did I mention SSIS sucks?
_______________________________________________________________
June 15, 2011 at 9:42 am
michael wang-201906 (6/15/2011)
i found the same issue on MSDN, seems 'a file that sometimes contains an extra CRLF at the end of the file' cause the problem.
The problem is exactly the opposite...the last row is missing a CRLF, not that it has an extra one.
If you define your rows to contain some columns with a trailing CRLF and the row does not contain a CRLF then what did you expect?
i really don't want to turn a simple data transfer task to a script task! pls help.
Ask your data supplier to provide a consistent file or add a CRLF to the file yourself. It's a one-line PowerShell command, i.e. no Script Task necessary.
Add-Content "C:\file.txt" ""
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply