70-467 · Question #163
You are creating a product dimension table and a SQL Server Integration Services (SSIS) package that will load the table. You need to keep a history in the table of changes to the names of products…
The correct answer is A. Add a Slowly Changing Dimension transformation to the package. E. Create an end date column in the table. F. Create a start date column in the table. To track the history of product name changes in a dimension table, a Slowly Changing Dimension Type 2 implementation is required, which uses start and end date columns to record the validity period of each version of a record.
Question
You are creating a product dimension table and a SQL Server Integration Services (SSIS) package that will load the table. You need to keep a history in the table of changes to the names of products. Which three actions should you perform? Each Answer presents part of the solution.
Options
- AAdd a Slowly Changing Dimension transformation to the package.
- BEnable Change Data Capture for the table.
- CCreate an inferred member column in the table.
- DFrom the Slowly Changing Dimension Wizard, set the name column to Type 3.
- ECreate an end date column in the table.
- FCreate a start date column in the table.
How the community answered
(41 responses)- A78% (32)
- B7% (3)
- C12% (5)
- D2% (1)
Why each option
To track the history of product name changes in a dimension table, a Slowly Changing Dimension Type 2 implementation is required, which uses start and end date columns to record the validity period of each version of a record.
Adding a Slowly Changing Dimension transformation enables SSIS to detect changes in dimension attributes and route rows to the appropriate output for inserting historical records, which is the core mechanism for implementing SCD Type 2 in a package.
Change Data Capture captures row-level changes in SQL Server source tables for downstream consumption but does not itself implement the historical versioning logic needed in a dimension table.
An inferred member column is used to handle dimension members that are referenced by fact records before the dimension record has been fully loaded, not for tracking historical name changes.
Type 3 SCD stores only the current value and one previous value in separate columns of the same row, which does not preserve a full history of all name changes over time.
An end date column is required by SCD Type 2 to mark when a historical version of a product record became inactive, allowing queries to identify which record was current during any given time period.
A start date column is required by SCD Type 2 to record when each version of a product record became effective, forming the lower bound of the validity interval alongside the end date.
Concept tested: SSIS Slowly Changing Dimension Type 2 implementation
Source: https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/slowly-changing-dimension-transformation
Topics
Community Discussion
No community discussion yet for this question.