Status Code vs Status Description
3 posters
Page 1 of 1
Status Code vs Status Description
Hello,
In dimensional modeling do we store Status code or Status description in the dimension. (e.g. Policy Status code 'POL', Description 'Policy').
Do we use mapping tables as separate tables?
Thank you
In dimensional modeling do we store Status code or Status description in the dimension. (e.g. Policy Status code 'POL', Description 'Policy').
Do we use mapping tables as separate tables?
Thank you
vanamali- Posts : 7
Join date : 2013-10-30
RE:Status Code vs Status Description
Hi,
you can store them in a dimension table, you can create a common dimn table (junk dimension) to store this type of information.
http://en.wikipedia.org/wiki/Dimension_(data_warehouse)
thanks
Himanshu
you can store them in a dimension table, you can create a common dimn table (junk dimension) to store this type of information.
http://en.wikipedia.org/wiki/Dimension_(data_warehouse)
thanks
Himanshu
hkandpal- Posts : 113
Join date : 2010-08-16
Re: Status Code vs Status Description
Sorry, my question was
In the policy dimension should I store the 'Policy Status ID' (with a separate status table that contains status id and status description) OR should I store the 'Policy Status Description'
In the policy dimension should I store the 'Policy Status ID' (with a separate status table that contains status id and status description) OR should I store the 'Policy Status Description'
vanamali- Posts : 7
Join date : 2013-10-30
Re: Status Code vs Status Description
You should always store all attributes of an object in the dimension that models that object - so the answer to your question is you store the ID and the description in the Dimension
This is one of the key differences between a transactional model and a dimensional model. What you are describing is essentially a transactional model in 3NF - where the object is to reduce/eliminate redundant data, by putting descriptions in a separate table and referencing them with codes. However in a Dimensional model it is expected that data is heavily duplicated.
This is one of the key differences between a transactional model and a dimensional model. What you are describing is essentially a transactional model in 3NF - where the object is to reduce/eliminate redundant data, by putting descriptions in a separate table and referencing them with codes. However in a Dimensional model it is expected that data is heavily duplicated.
nick_white- Posts : 364
Join date : 2014-01-06
Location : London
Re: Status Code vs Status Description
Thank you...I got my answer.
vanamali- Posts : 7
Join date : 2013-10-30
Similar topics
» Is it a good idea to have a single STATUS table if we have to store multiple status in the data mart?
» Transaction description
» How to handle several single description field dimensions
» Booking number and description in the fact table?
» Whether to use additional column or use existing
» Transaction description
» How to handle several single description field dimensions
» Booking number and description in the fact table?
» Whether to use additional column or use existing
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum