> I have a package using foreach loop to load flat files. Some of the
> files/transfer may fail for different reasons at different tasks. I
> want to have a summary report shows the succeeded and failed files at
> the end (maybe using sending mail task to send).
>
> What's the best way to generate the summary report? One way may be
> adding a Script task following every task to write the error to a SQL
> table. It sounds very cumbersome...
>

> Thanks.
>
> The SSIS package will be called by an Asp.net app and the summary
> result report will be displayed in a gridview. The log sounds too free
> style and how to output the log at the end?
>
> "Allan Mitchell" wrote:
>
>> Hello nkw,
>>
>> Seeing as Event Handlers flow up you could of course write the
>> logging step to the package's event handler. The variable
>> System::SourceName would tell you which task was the one reporting
>> the event.
>>
>> --
>>
>> Allan Mitchell
>> http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com
>> |
>> http://www.konesans.com
>>> I have a package using foreach loop to load flat files. Some of the
>>> files/transfer may fail for different reasons at different tasks. I
>>> want to have a summary report shows the succeeded and failed files
>>> at the end (maybe using sending mail task to send).
>>>
>>> What's the best way to generate the summary report? One way may be
>>> adding a Script task following every task to write the error to a
>>> SQL table. It sounds very cumbersome...
>>>