You design a Business Intelligence (BI) solution by using SQL Server 2008. You plan to design a logging strategy for all SQL Server 2008 Integration Services (SSIS) packages for your company. You want to log errors that occur in all existing and future packages to a SQL Server 2008 table.
You need to design the strategy to meet the following requirements:
-The logging mechanism must be reused by each package.
-Changes to the logging mechanism must be applied to all packages by using the minimum amount of administrative effort.
What should you do?
A.
Enable and configure logging in a package.
Create all other packages by using the first package as the template.
B.
Create an event handler in a package.
Configure the event handler to perform logging.
Create all other packages by using the first package as the template.
C.
Enable and configure logging in a package.
Save the log settings to an XML file.
Enable logging in all other packages.
Load the log settings on each package by using the XML file.
D.
Create an event handler in a package.
Configure the event handler to perform logging.
Enable package configurations in the package.
Store the properties of the event handler in an XML configuration file.
Configure all the packages to use the configuration file during execution.
Explanation:
Tip: "logging mechanism" = "XML"Logging
Because Integration Services packages are, for the most part, designed for unattended operation, it can be extremely important to create a log documenting the execution of the package. This type of execution log can also be helpful for testing and debugging during the creation of the package. We control the logging performed by an Integration Services package using the Configure SSIS Logs dialog box.
We can create the following types of logs:
c Comma-separated values text file
c File to be read by the SQL Profiler
c SQL Server Table named sysdtslog90
c Windows Event Log
c Extensible Markup Language (XML) text file
All of the log types, with the exception of the Windows Event Log, need to be configured to specify exactly where the logged information is to be stored.
Finally, we need to determine which events should be logged for the package or for a package item.
(McGraw-Hill – Delivering Business Intelligence with Microsoft SQL Server 2008 (2009)