we have a discussion about designing a data warehouse. One suggestion
was to have all business ratios as dimension. The fact table is a
combination of some diemnsions plus the business ratio dimension. These
relationships are building the primary key and then there is one value
column.
I am not really sure if that is a really good design because of the
maintenance effort. I would prefer to have maybe an indexed view for
that. Has anybody used a design like that ?
Multiple Hierarchy ...Multiple Hierarchy created huge aggregations?!... its common source from the dimension table. ... tried to design my cube using multiple hierarchy and found ... (microsoft.public.sqlserver.olap)
Business ration as dimension ?! ... One suggestion... was to have all business ratios as dimension. ... combination of some diemnsions plus the business ratio dimension.... I am not really sure if that is a really good design because of the ... (comp.databases.olap)
Re: engineering drawing question ... > I got the following question on my first year engineering design... > drawings have true dimensions on x,y,z axes). ... In my 40 years-of-engineering-world (PE, in machine design,... a design-build and of a consulting firm) a "dimension" is the value ... (sci.engr.mech)
Re: Using ProE after SolidWorks - how hard can that be? ... I did a review of a design I had ...(fucking clueless manager who NEVER really used Pro/ ... everything but you could drag a line and the dimension would change. ... The interface sux.... (comp.cad.solidworks)
Re: Interesting MDX problem ... I think your design is not normal. ... > the dimension tables for each of these by foreign keys. ... > CourtSportsCount: Count of people playing Tennis or Badminton or both. ... If I then slice on the ... (microsoft.public.sqlserver.olap)
