Dimension Version Field Variations you've seen.
Page 1 of 1
Dimension Version Field Variations you've seen.
I've always followed the Kimball standard of using RowIsCurrent (Single Character), and RowStartDate and RowEndDate as the SQL Server Date, or Datetime datatypes.
I'm polishing up a script which writes T-SQL Merge statements based upon SCD type (0,1,2) for each field automatically. With the exception of the field names, what other configurations of expiration fields have you seen? I want to make sure my script handles most of what's out there.
Also, what term would you use to refer to these fields? Versioning fields? Expiration Fields? I need to have a way to refer to these types of fields in the script and in the documentation.
I'm polishing up a script which writes T-SQL Merge statements based upon SCD type (0,1,2) for each field automatically. With the exception of the field names, what other configurations of expiration fields have you seen? I want to make sure my script handles most of what's out there.
Also, what term would you use to refer to these fields? Versioning fields? Expiration Fields? I need to have a way to refer to these types of fields in the script and in the documentation.
DavidStein- Posts : 24
Join date : 2010-04-01
Similar topics
» Date Dimension or DateTime Field
» dimension model for many indicators field
» How to track the change of a specific field in a dimension table?
» Avoiding Nulls in Dimension Tables
» A new version of ISO Standard SQL has just been approved and published
» dimension model for many indicators field
» How to track the change of a specific field in a dimension table?
» Avoiding Nulls in Dimension Tables
» A new version of ISO Standard SQL has just been approved and published
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum