You develop a SQL Server Integration Services (SSIS) package in a project by using the Project
Deployment Model. It is regularly executed within a multi-step SQL Server Agent job.
You make changes to the package that should improve performance.
You need to establish if there is a trend in the durations of the next 10 successful executions of the
package. You need to use the least amount of administrative effort to achieve this goal.
What should you do?
A.
After 10 executions, view the job history for the SQL Server Agent job.
B.
After 10 executions, in SQL Server Management Studio, view the Execution Performance subsection
of the All Executions report for the project.
C.
Enable logging to the Application Event Log in the package control flow for the OnInformation event.
After 10 executions, view the Application Event Log.
D.
Enable logging to an XML file in the package control flow for the OnPostExecute event. After 10
executions, view the XML file.
Explanation:
The All Executions Report displays a summary of all Integration Services executions that have been
performed on the server. There can be multiple executions of the sample package. Unlike the
Integration Services Dashboard report, you can configure the All Executions report to show executions
that have started during a range of dates. The dates can span multiple days, months, or years.
The report displays the following sections of information.
* Filter
Shows the current filter applied to the report, such as the Start time range.
* Execution Information
Shows the start time, end time, and duration for each package execution.You can view a list of the
parameter values that were used with a package execution, such as values that were passed to a child
package using the Execute Package task.
B