Consolidating error rows

  • Attached is a technique I will be using to collect error rows from

    various components in a dataflow.

    Since the dataflows I am working with have 3-4 transformations within each one, this is going to get pretty tedious.

    I have the rows going to a "logDetail" flat file for later analysis. Most likely to be a database table eventually.

    Is there a better way to collect and consolidate error rows?

    Thanks

  • I can't really think of a better way to do this.

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

  • This is perhaps the only way (most people know of).

    BTW , why are you looking for an alternative way of doing this?

  • I am looking for a slick alternative to minimize clutter in the package.

  • Also I don't want to hear about something better down the road. Is it common in a large

    ETL to have an error output from every component in the DF?

  • hurrican3p (6/6/2012)


    Is it common in a large ETL to have an error output from every component in the DF?

    I always have an error output for each task in the dataflow; my thinking is to make it easier to pinpoint problems down to the specific task when/if they occur.

    Rob

  • I wanted to use an event handler but it seems that the Redirection doesn't raise any events

  • hurrican3p (6/6/2012)


    I am looking for a slick alternative to minimize clutter in the package.

    I don't really see the issue.

    Every component has an error path. You combine them with a union all and you write everything to the log file.

    What's the clutter?

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

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

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