• It would be good to see the package, as I am very confused by the article.

    It does not include details of the command being executed, so its difficult to know what errors might be anticipated.

    It does not include details of how error-handling was configured on the command component, so we cannot tell how we would expect any anticipated errors to be handled.

    It does not include the error information reported on the Progress tab (or in the logs) which includes the OLEDB errors that would describe why the command failed - especially useful for errors that are either not explicitly handled by error options, or for which the error-handling options are just set to failure.

    Also, the article seems to describe a classic Slowly Changing Dimension scenario - and SSIS includes a wizard that builds those processes very easily including full handling of inserts and updates. The flows built by this wizard can be easily customized too.

    I can understand David's frustration that he is finding errors difficult to handle, and for sure we must improve the ease of use of this very powerful feature in future versions. For now, however, I do believe we have the most flexible row-by-row error handling that I have seen in a data integration tool, and I think that even in this case we include all the information necessary to debug. But I simply cannot tell from the article.

    Donald Farmer

    Group Program Manager

    SQL Server Integration Services