My boss doesn't want me to build any SSIS packages based on
custom components. I personally would definitely give it a try but
he's the boss...
So everything looks good now except that my SSIS Logging stopped reporting any "OnError" events. I think all "OnError" events are now being intercepted by your Script.
That means I don't have a choice. I will have to turn off SSIS Logging
and completely switch to Error Script and rely on it. I liked SSIS Logging.
It was automated and very detailed. It was very convenient to monitor the progress of the package. For example, I used OnPipelineRowsSent event
and it reported how many rows were on each input and output for each task. Was kind of convenient.
But now it becomes incomplete. OnError event does not get logged.
So my plan now is to change [load_errors] table:
Rename it to "Messages"
Add "message" column and log package progress together with any errors that occur.
Like "Package BRANCH2.dtsx started" for example.
Or "214 records were processed"