redirecting (error) rows

Question

redirecting (error) rows

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

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

steveb. SSC-Forever Points: 46733 More actions · Answer 1

I have found the problem with using an error redirect on a destination is that it usually throws an error before it has a chance to re-direct the row.

What I would do in this situation is to use a data conversion transformation before the destination, you can then use this to specify the data type and lengths, and add a re-direction for any truncation that may occur. I find this is a lot safer than relying on the destination to reject the rows.

Jack Corbett SSC Guru Points: 184395 More actions · Answer 2

An SSIS destination will redirect error rows. I use it all the time. There can be an issue if you use Fast Load though.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

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

Mark F-428640

Hall of Fame

Points: 3659

December 2, 2008 at 11:19 am

#906413

Thanks Steveb that did the trick

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

Hey Jack thanks for your response yes I had the data access mode set to Table or view. Steve's answer was able to resolve my issue.

Cheers,

Jack Corbett SSC Guru Points: 184395 More actions · Answer 5

Mark,

I think I misread your original post. Were you trying to redirect errors from the Source Component or at the Destination?

I've never had an issue with the a truncation error at the destination causing a redirect of rows to fail. In fact whenever I have had source data defined larger than the destination the Package will not run at all because of a validation error.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

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

No I think you read it right my source data had a column defined as a Varchar(50) and the destination expected string of column length 3. The automation would run until it reached around the 200k mark (out of 1.3 million) and then fail. Adding the data conversion object just before the flat file destination object allowed the option to redirect the rows to OLE DB destination object (which I couldn't do with the flat file destination object). It moved 5 rows which were causing the trouble and allowed the rest of the records to be processed.

Regards,