Database Reference
In-Depth Information
Figure A-33
.
The finished Package Instance report
Clicking the Events link will take me to the Events report and display only the
events for the package instance on the referenced row.
To wrap it up, you can start at the Application Instance report; it is on the dash-
board. Click the Packages link to view all the SSIS child packages that executed as part
of the selected SSIS application instance. From there, drill into the Errors report and
observe the errors that caused a package to fail, or view all of the events recorded by
the OnInformation event handler for the selected package instance on the Events re-
port. You can reach all errors and events for an SSIS application instance from the Ap-
plication Instance report, as well.
Conclusion
This example isn't an exhaustive example of an SSIS framework, but it demonstrates
the utility of patterns-based data integration development using SSIS. The sample
framework provides repeatable, metadata-driven SSIS execution without leaving the
SSIS and SQL Server database domains. Monitoring is provided by a set of SQL Serv-
er Reporting Services reports driven by stored procedures that read metadata automat-
ically captured by the framework's
Parent.dtsx
SSIS package. Zero lines of code
are required in child packages to capture error and event information, and this informa-
tion is logged centrally in a consistent format, which makes it perfect for reporting.
