Modifying a Slowly Changing Dimension KM to allow undefined behaviors

When working with a slowly changing dimension, you may sometimes encounter a dimension table that has dozens (or perhaps hundreds) of attributes, making the task of setting the SCD behavior for each column very tiresome. There may also be occasions when business requirements dictate that all activity on a specific dimension table be captured historically, that is, all columns are considered to be the "trigger" fields.

In order to address these two situations, a few simple modifications can be made to the SCD IKM to allow the developer to avoid having to set the SCD behavior for every column. By making these simple modifications, the developer will only need to set the behaviors for the Surrogate Key, the Natural Key, the Active Flag, and The Starting and Ending date columns; all other columns will be implicitly managed as trigger fields by automatically setting the Add Row on Change condition.

Although it's certainly possible...