Database Reference
In-Depth Information
CHAPTER 15
Logging and Reporting Patterns
An essential part of managing any application is knowing what happens during the day-
to-day usage of the application. This theme holds especially true in ETL solutions in
which the data being manipulated can be used for reporting and analysis. Administrators
satisfy this need through logging and reporting of the executions, errors, and statuses of
the applications, which fits perfectly into the management framework concept.
The past few chapters have discussed how to set up other pieces of the management
framework, including how to execute parent-child packages and how to implement cent-
ralized custom logging. This chapter will describe how to use the built-in logging in In-
tegration Services to report on all aspects of an Integration Services application.
Integration Services provides two primary methods to help satisfy the logging and
reporting need.
• Package logging and reporting
• Catalog logging and reporting
Let's walk through how to set up each of these methods and then utilize patterns that
best highlight these methods.
Package Logging and Reporting
The package logging and reporting method has been around since the first edition of In-
tegration Services. This method is characterized by setting up logging during develop-
ment of the package. A logging provider can log to different outputs, including SQL
Search WWH ::




Custom Search