June 5, 2012 at 7:00 pm
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
June 6, 2012 at 12:06 am
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
June 6, 2012 at 4:49 am
This is perhaps the only way (most people know of).
BTW , why are you looking for an alternative way of doing this?
June 6, 2012 at 7:18 am
I am looking for a slick alternative to minimize clutter in the package.
June 6, 2012 at 7:27 am
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?
June 6, 2012 at 7:37 am
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
June 6, 2012 at 9:27 am
I wanted to use an event handler but it seems that the Redirection doesn't raise any events
June 6, 2012 at 1:05 pm
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
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy