Question

Any simple way of solving the problem where you have a component and get the same log massage more than one time due to the fact that the component is nested inside other components (like a container and a data flow for example)

I found this, where MS say it wont do anything about it, but its from 2007.
I dont really want to do the workaround suggested, seems a lot of work.

Answer 1

For logging, if you chose to log to sql server, SSIS will create a Stored Proc
(SQL 2005)

Proc Name: dbo.sp_dts_addlogentry

Table Name: dbo.sysdtslog90 (user table)

(SQL 2008)

Proc Name: dbo.sp_ssis_addlogentry

Table Name: dbo.sysssislog (system table)

You are free to modify this to filter out log entries (sql will recreate it if it is missing, but will not overwrite a self written version of the same name.)

The system generated version is simply an insert into of the parameters sent to the proc by SSIS.

You can add logic to follow the chain up the executionid to find parent objects and suppress logging for entries that have already been logged (you will want to handle the OnError event name in your code for this) I usually pass OnPreExecute, OnPostExecute, OnError, and OnTaskFailed events into my logging proc. By default, the proc also gets PackageStart and PackageEnd events.

That being said, I let all of these log fully to the table in sql then use summary and detail report to check the logging and see errors. My report filters to show only the one error for each occurance rather than filtering on the input into the log file. I also log all of my SSIS packages into a single database for configurations and logging that is included in every SSIS package.