nerdexam
Microsoft

70-467 · Question #74

You need to create the Package Activity report. What should you do?

The correct answer is D. Create an SSRS report that uses the catalog.executions and. The SSISDB catalog views such as catalog.executions provide built-in execution history, making an SSRS report against them the most direct way to produce a Package Activity report.

Design an ETL solution (Extract, Transform, and Load)

Question

You need to create the Package Activity report. What should you do?

Options

  • ACreate a log table and use SSIS event handlers to write to the log table.
  • Buse the SSIS log provider for SQL Server.
  • CCreate a log table and build a custom log provider to write to the log table.
  • DCreate an SSRS report that uses the catalog.executions and

How the community answered

(47 responses)
  • A
    9% (4)
  • B
    15% (7)
  • C
    4% (2)
  • D
    72% (34)

Why each option

The SSISDB catalog views such as catalog.executions provide built-in execution history, making an SSRS report against them the most direct way to produce a Package Activity report.

ACreate a log table and use SSIS event handlers to write to the log table.

Writing to a custom log table via SSIS event handlers requires adding event handler tasks to every package and maintaining a custom schema, adding unnecessary complexity when catalog views already exist.

Buse the SSIS log provider for SQL Server.

The SSIS log provider for SQL Server writes to the sysssislog table in msdb, which has a fixed schema not designed for flexible package activity reporting.

CCreate a log table and build a custom log provider to write to the log table.

Building a custom log provider requires .NET development effort and ongoing maintenance, far exceeding what is needed when the SSISDB catalog already tracks execution data.

DCreate an SSRS report that uses the catalog.executions andCorrect

The SSISDB catalog exposes system views like catalog.executions, catalog.event_messages, and catalog.executable_statistics that store detailed package run history without any custom logging code. Building an SSRS report on top of these views leverages already-captured data and avoids maintaining a custom logging infrastructure.

Concept tested: SSISDB catalog views for package execution reporting

Source: https://learn.microsoft.com/en-us/sql/integration-services/system-views/catalog-executions-ssisdb-database

Topics

#SSIS catalog#SSIS logging#catalog.executions#execution reporting

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-467 Practice