A had a quick glance through the article. The title says it's about CDC, but I don't see anything about the change data capture functionality introduced in SQL Server 2008. Instead, you roll your own alternative.
In the first dataflow, you do a full outer join between the staging table and the destination table. Can't that introduce locking? Suppose you have a very large dimension and the source is still reading while you are already inserting new rows. Since the OLE DB Destination with Fast Load takes by default a table lock, this might introduce issues.
Your article starts with the following sentence:
Within Integration Services there is no single out of the box components to handle CDC
That is simply not true. There are build-in components available for CDC in SSIS 2012 (CDC Control Task, CDC Source and CDC Splitter). This article is published in june 2012, and SQL Server 2012 has been publicly available for some time now, so you can't just ignore that edition.
In my opinion, the solution this article proposes is very good for SQL Server 2005, but not needed anymore starting from SQL Server 2008 (unless you don't have Enterprise Edition of course).
edit: if Enterprise Edition is not availabe, I would rather consider the MERGE statement for SQL Server 2008 and up.
How to post forum questions.Need an answer? No, you need a question.What’s the deal with Excel & SSIS?
My blog at SQLKover
MCSE Business Intelligence - Microsoft Data Platform MVP