You are troubleshooting an existing SQL Server Integration Services (SSIS) package. On several occasions, the package execution does not finish and no data seems to have been transferred. You need…

Question

Options

• ARun the dtutil command to deploy the package to the SSIS catalog and store the
• BUse an msi file to deploy the package on the server.
• COpen a command prompt and execute the package by using the SQL Log provider and
• DCreate a reusable custom logging component and use it in the SSIS project.
• EOpen a command prompt and run the dtutil/copy command.
• FConfigure the SSIS solution to use the Project Deployment Model.
• GAdd an OnError event handler to the SSIS project.
• HOpen a command prompt and run the gacutil command.
• IOpen a command prompt and run the dtexec/dumperror/conn command.
• JOpen a command prompt and run the dtexec/rep/conn command.

• A
  3% (1)
• C
  84% (27)
• E
  9% (3)
• G
  3% (1)

Explanation

Running the package from the command prompt using dtexec with the SQL Log provider (via the /logger or /l switch referencing the SQL Server log provider) enables logging without modifying the package source, re-deploying it, or writing custom code. This satisfies the 'minimize deployment and development effort' constraint. Deploying to the SSIS catalog (A) or using an MSI (B) involves deployment changes. Building a custom logging component (D) requires significant development. Running dtutil/copy (E) just copies the package. Switching to the Project Deployment Model (F) is a larger architectural change. Adding an event handler (G) requires opening and saving the package. gacutil (H) installs assemblies to the GAC-unrelated. dtexec /dumperror (I) creates memory dumps on error but does not set up standard logging. dtexec /rep (J) controls console reporting, not persistent log records.

No community discussion yet for this question.