Biml and SSIS Frameworks - SQL Server Integration Services Design Patterns - page 542

ence constraint ( OnFailure ) from the Execute Child Package Execute Package task
to the Log Package Failure Execute SQL task.
Test the package instance logging by running a few test executions. Allow one to
succeed and the other to fail. When you check the Application and Package Instance
tables, the results should appear as shown in Figure A-15 .
Figure A-15 . Examining the application and package instance logs
You can tell by examining the Application Instance and Package Instance log tables
that AppInstanceID8 started at 6:47:24 PM 29 Jun 2014. You can also see three
SSIS packages—with PkgInstanceID 's 10, 11, and 12—were executed as part of
the SSIS application. Each package succeeded, and the SSIS application succeeded as
well. You also know AppInstanceID7 started at 6:14:15 PM 29 Jun 2014 and ex-
ecuted PkgInstanceID 's 7, 8, and 9. PkgInstanceID 's 7 and 8 succeeded, but
PkgInstanceID 9 failed; failing the SSIS application.
Cool? Cool. Let's move to error and event logging.
Building Error Logging
Instrumenting data integration processes to capture and preserve error and exception
metadata is the most important and useful type of logging. Exceptions and errors are
going to happen. SSIS provides a fairly robust model for capturing and reporting errors