If you’re looking for a way to add the logical error description into your dataflow, you may want to use a common Script Component with these lines of Visual C# script (overwrite the existing procedure):
public override void Input0_ProcessInputRow(Input0Buffer Row)
Row.ErrorDescription = this.ComponentMetaData.GetErrorDescription(Row.ErrorCode);
But if you also want to add the specific column name on which the error occured, take a look at this customer SSIS component.
EOD in action:
How to install this BIDS 2008R2 component?
Step 1) Extract the ZIP-file
Error Output’s Description on CodePlex
Here’s a rebuild version of the original version 2.0.0 ErrorOutputDescription.dll library (Windows 7 and VS2010) which should be more friendly in Win7:
(Rename the file extension to *.zip, WordPress doesn’t allow ZIP-files)
Step 2) Open a command-windows (search for ‘cmd’) and ‘Run as Administrator’, then execute the Install.bat file.
Step 3) Enable the custom component in BIDS so that it will be listed in the Toolbox:
Go to Tools -> Choose Toolbox Items (in BIDS)
Select the Error Output Description’s DLL and click on ‘OK’.
It should now be selectable in the Toolbox:
If you’re having problems with this component (it can be a bit buggy), a quick work around is to delete all dataflow components down-stream of the EOD-component and possibly rebuild the package, before you edit the EOD-component.
Other discussions about this custom component can be found here.
But…after all…it works great once you get it running 😀
You may want to use the column name to zoom in on the incorrect values which were found during processing.
A practical example of such a report can be found here.