Fast Changing Dimension

• Simon Hundleby

  SSCarpal Tunnel

  Points: 4564

  More actions

  May 18, 2015 at 9:28 am

  #300784

  Hi I have a table that needs to be incorporated into the data warehouse.

  The table has the following schema.

  CREATE TABLE [dbo].[Consignment](

  [Id] [int] IDENTITY(1,1),

  [BooingID] INT

  [BookingDate] [datetime] NULL,

  [CarrierServiceName] [nvarchar](255) NULL,

  [CarrierServiceCode] [nvarchar](255) NULL,

  [OriginAddressCompanyName] [nvarchar](255) NULL,

  [OriginAddressAddressLine1] [nvarchar](255) NULL,

  [OriginAddressAddressLine2] [nvarchar](255) NULL,

  [OriginAddressAddressLine3] [nvarchar](255) NULL,

  [OriginAddressTownOrCity] [nvarchar](255) NULL,

  [OriginAddressCountyOrState] [nvarchar](255) NULL,

  [OriginAddressPostcode] [nvarchar](255) NULL,

  [OriginAddressCountry] [nvarchar](255) NULL,

  [OriginAddressCountryCode] [nvarchar](255) NULL,

  [OriginAddressThreeLetterCountryCode] [nvarchar](255) NULL,

  [OriginAddressThreeDigitCountryCode] [nvarchar](255) NULL,

  [OriginContactTitle] [nvarchar](255) NULL,

  [OriginContactForename] [nvarchar](255) NULL,

  [OriginContactSurname] [nvarchar](255) NULL,

  [OriginContactTelephoneNumber] [nvarchar](255) NULL,

  [OriginContactMobileNumber] [nvarchar](255) NULL,

  [OriginContactEmailAddress] [nvarchar](255) NULL,

  [DestinationAddressCompanyName] [nvarchar](255) NULL,

  [DestinationAddressAddressLine1] [nvarchar](255) NULL,

  [DestinationAddressAddressLine2] [nvarchar](255) NULL,

  [DestinationAddressAddressLine3] [nvarchar](255) NULL,

  [DestinationAddressTownOrCity] [nvarchar](255) NULL,

  [DestinationAddressCountyOrState] [nvarchar](255) NULL,

  [DestinationAddressPostcode] [nvarchar](255) NULL,

  [DestinationAddressCountry] [nvarchar](255) NULL,

  [DestinationAddressCountryCode] [nvarchar](255) NULL,

  [DestinationAddressThreeLetterCountryCode] [nvarchar](255) NULL,

  [DestinationAddressThreeDigitCountryCode] [nvarchar](255) NULL,

  [DestinationContactTitle] [nvarchar](255) NULL,

  [DestinationContactForename] [nvarchar](255) NULL,

  [DestinationContactSurname] [nvarchar](255) NULL,

  [DestinationContactTelephoneNumber] [nvarchar](255) NULL,

  [DestinationContactMobileNumber] [nvarchar](255) NULL,

  [DestinationContactEmailAddress] [nvarchar](255) NULL,

  CONSTRAINT [PK__Consignm__3214EC074707859D] PRIMARY KEY CLUSTERED

  (

  [Id] ASC

  )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY],

  This Table has the same granularity as the fact table as it’s one row per booking.

  However due to the nature of the data I would not want to incorporate this into the fact table.

  The Originating and Destination addresses are populated for each booking and are required for reporting.

  Question

  Should this be moved into a fast changing Dimension table.?

  or would there be a better way to incorporate this data.

• Alvin Ramard

  SSC-Forever

  Points: 41190

  More actions

  May 18, 2015 at 9:37 am

  #1798675

  There's different ways to handle this, but if you had a Originating_key and Destination_key columns in your fact table, you would have to deal with changing dimensions.

  ---

  
  Alvin Ramard
  Memphis PASS Chapter[/url]

  All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

  For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]