Best Practice - Device membership dimensions
i have table of agents, agent groups , agent group members. agent can in many agent groups. agent group members table links agent , agent group together.
what best practice creating dimension , user defined hierarchy support this.
as user of cube may want browse data agent , may want browse agent group (seeing 1 line each agent)
is there best practice this?
i think agent browsing use agent dimension.
i agent group broseing use agent group dimension. means have expand agent group dimension include agent , agentgroupmembers tables. attribute relationships. understand how country, state, city. agent group hierarchy have have agent group key, agent key , agentgroupmembers key?
hi,
1) can create single table contains agents & groups , create hierarchy agents groups -> agents. or if want keep both dimension tables separate can create hierarchy using both tables. check "product" dimension adventureworks sample same.you can download sample database codeplex;
2) if each agent belongs multiple agent groups can create many-to-many dimension.refer following whitepaper;
http://msdn.microsoft.com/en-us/library/ms345139(sql.90).aspx
http://technet.microsoft.com/en-us/library/ms170463.aspx
http://www.sqlbi.com/default.aspx?tabid=80
aniruddha
SQL Server > SQL Server Analysis Services
Comments
Post a Comment