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 |
jbphoenix
Yak Posting Veteran
68 Posts |
Posted - 2009-01-23 : 15:59:50
|
My package imports a flat file should have 10,000 rows. But by the time the data makes it to the ole db destination there are only 5,100 rows. My package goes like this - flat file source -> data conversion on 3 fields -> ole db destination. I have it ignoring errors because of the description field which kept saying there was a truncation issue. The field sizes are plenty big so I just decided to ignore the errors. I'm not sure where my other 5,000 rows are going. |
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2009-01-23 : 18:06:25
|
If you're ignoring the truncation errors I'd be really concerned about how many you're losing because of it. Can you dump the errors out into a file or put a data reader on it so you can see how many you're losing to the errors? Just like in tsql when you get the "data would be truncated" error doing an insert, ssis is going to dump those that would have the problem.Mike"oh, that monkey is going to pay" |
 |
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-24 : 13:00:36
|
maybe you could apply substring on description column to take only part of string you want to avoid truncation |
 |
|
|
|
|