1

Closed

Enable SCD 2 Date Handling Effective and Expiry Dates Set to SSIS Variable Values

description

Current support for explicit date is nice but prefer not hard coding in component.
Propose adding option to set these values from SSIS variables to enable these values to be changed via any SSIS supported way to change variable values such as using variable value property expressions or package configuration. (Example: designer creates RowDefaultStartDate and RowDefaultEndDate variables to use within the component.)
Closed by

comments

JoeSalvatore wrote Mar 3, 2010 at 1:03 AM

Other work items within the Issue Tracker are related to this:
Support Multiple Intra-day SCD Processing http://kimballscd.codeplex.com/WorkItem/View.aspx?WorkItemId=2318
Add Support for a "Change Stream" Source System Input http://kimballscd.codeplex.com/WorkItem/View.aspx?WorkItemId=304
Please vote and add your additional insights.

toddmcdermid wrote Mar 30, 2010 at 10:58 PM

There'll only be room for the one - the "default expiry". The default effective is the "now" value (as modified by the choice for "new starts...").

luisefigueroa wrote Feb 17, 2011 at 9:06 PM

I am using change data capture to retrieve changes from the source. It would be nice if i could use the timestamp associated to the lsn of every row associated with the insert or change./ in other words I would pass the start date and end date as an input column.

Sign in to add a comment