sql - Data Warehouse - duplicate dimension members for multiple divisions -


i new data warehousing , ssis, have been tasked populating data warehouse sales transaction records 2 different divisions of parent company. issue...i modifying ssis package populates product (skus) dimension accommodate products pertain 2 divisions , have ended few product names exist in both divisions. need solution accommodate product list each division in same dimension table. possible??

to illustrate:

https://www.dropbox.com/s/hkda4n1bfs5o178/capture.jpg?dl=0

where 'widget_3' , 'widget_4' named same in both divisions, not same product. happened named same. imagine common problem, reluctant make changes dimension table schema before consulting first.

i working product dimension table has [memberid] primary key , [product] unique non clustered constraint ignore_dup_key = off. first instinct modify table schema change ignore_dup_key on , rely on having [division] attribute populate data in fact table; use [product] , [division] identify [memberid] on update.

something this??:

https://www.dropbox.com/s/fjzvsh80mtp3ozs/capture2.jpg?dl=0

am going down wrong path?

notes: - using sql 2008

this @ end of day business problem. if there name conflict in 2 department conflict should resolved before present data togheter, else department find see sales on product not belong them.

once understood how treat @ global level (for example have small department prefix in case of clash, has agreed) problem automatically solved.

when departments not reached or not agree on solution, have 2 product name column, each every of 2 department , use them togheter pk (i not include division, or @ least not show it, because confusing end users). recommend find business solution, not technical one.


Comments

Popular posts from this blog

c# - Better 64-bit byte array hash -

webrtc - Which ICE candidate am I using and why? -

php - Zend Framework / Skeleton-Application / Composer install issue -