alternate approaches for late arriving dimension attributes

View previous topic View next topic Go down

alternate approaches for late arriving dimension attributes

Post  karthiksm on Sun Oct 20, 2013 12:11 pm

I have a scenario where I have more than one late arriving dimension attribute (eg : status, interest type etc) in a type 2 dimension and the effective date (which is retroactive) of these attributes could be different from each other and its possible both can arrive late on the same load. Since the effective and expiry date in this dimension applies to the entire record, how to manage different effective dates for these attributes in this case? Is it OK to separate these attributes in to another child dimension similar to the creating a new dim for rapidly changing dim attributes? Even this may not solve due to different effective dates. Appreciate any help or insights to resolve this.

karthiksm

Posts : 2
Join date : 2013-10-20

View user profile

Back to top Go down

Re: alternate approaches for late arriving dimension attributes

Post  ngalemmo on Sun Oct 20, 2013 3:26 pm

There is a lot you need to consider:

How late is late? Given this is a type 2, what about the facts already loaded? Do they need to be rekeyed?

How different are the timestamps of these attributes? Seconds, minutes, hours, days? What really makes sense from a business point of view? Do small differences really matter? Its one thing to be technically accurate, but does it really matter?
avatar
ngalemmo

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

View user profile http://aginity.com

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum