You are designing a SQL Server Integration Services (SSIS) data flow to load sales transactions from a source system into a data warehouse hosted on SQL Azure. One of the columns in the data source is

Question

Options

• AAudit
• BSource Assistant
• CDestination Assistant
• DScript Component

• A
  12% (3)
• B
  4% (1)
• C
  4% (1)
• D
  80% (20)

Explanation

The requirement is to route rows into separate processing streams based on a ProductCode value - this is a conditional routing scenario. The ideal built-in transformation for this is Conditional Split, but it is not among the listed options. The Script Component (configured as a transformation) can be programmed with multiple defined outputs and custom .NET logic to inspect each row's ProductCode and direct it to the appropriate output. It is the only listed option capable of implementing dynamic row-routing logic. Option A (Audit) only appends package metadata columns (like ExecutionID) to the data flow. Option B (Source Assistant) and Option C (Destination Assistant) are design-time wizards for creating source/destination adapters, not transformations that manipulate data flow rows.

No community discussion yet for this question.