Replacement of SCD Task : Kimball Method SSIS Slowly Changing Dimension Component

The credit of this post goes to the one who made an anonymous comment on my previous post on which I wrote about SCD Task optimization. Below are the features that KimballSCD SSIS Component offers as per its home page. Thou I have not used it yet, but it's definitely on my evaluation list now.

Features:

• One component on the design surface that can be edited without adverse effects on the rest of the Data Flow. (As opposed to the SCD Wizard that creates multiple components that are destroyed and rebuilt if the Wizard is run again.)
• Insane performance - measured to be 100x superior by use of multiple threads, sort optimization, and implied outcome determination. (As opposed to using the SCD Wizard with single-threaded uncached row-by-row lookups.)
• Surrogate Key management. (As opposed to zero support in the SCD Wizard.)
• "Special" (unknown) member support, per Kimball Method best practices. (As opposed to zero support in the SCD Wizard.)
• Includes a "row change reason" output column on all (except Unchanged) outputs, per Kimball Method best practices. (As opposed to zero support for debugging why a row was directed to a particular output in the SCD Wizard.)
• Supports simple and advanced styles of Row Auditing for inserts and updates, per Kimball Method best practices. (As opposed to zero auditing support in the SCD Wizard.)
• Flexible column comparisons: case (in)sensitive and space (in)sensitive as desired, plus culture-sensitivity. (As opposed to zero support in the SCD Wizard.)
• Flexible SCD 2 "current row" handling - permits specification of the date "endpoints". (As opposed to the SCD Wizard requiring the "expiry" date be NULL only.)
• Flexible SCD 2 date handling - permits specification of what date expired and new rows get marked with. (As opposed to the SCD Wizard leaving that up to a Derived Column component that will get destroyed when the Wizard is run again to add/fix other properties.)
• Reads the existing dimension from the Data Flow, not a Connection Manager - allowing the package designer to cache the existing dimension table as they see fit. (As opposed to the SCD Wizard that only supports some OLE DB Connection Managers.)