If you wish to use the the dept dimension in 2 different "roles", then
this post may help:
http://groups-beta.google.com/group/...rver.olap/msg/
990c17795e0cf8eb
Quote:
|
Newsgroups: microsoft.public.sqlserver.olap
|
From: Deepak Puri <deepak_p... (AT) progressive (DOT) com>
Date: Wed, 13 Apr 2005 15:39:35 -0700
Subject: Re: Multiple date dimensions for a cube - how best to
structure?
In my own experience, I've either created multiple views of the SQL
table; or, as you are suggesting, created multiple dimensions from the
same SQL table. A couple of issues to keep in mind with the second
option:
- Aliases for the table are needed in the cube schema, with an instance
for each dimension that uses the table.
- In my case, drill-through to details didn't work as expected for the
cube (don't know if this is still an issue).
Pl. note that AS 2005 (Yukon) allows use of a dimension in multiple
roles, which is a simpler solution:
http://www.microsoft.com/techn*et/pr...lua*te/dwsqlsy
..m
spx
Business Intelligence and Data Warehousing in SQL Server 2005
..
Analysis Services 2005 adds important new dimensional structures. Some
of these structures have odd names, but these names are common in the BI
literature.
• Role Playing: The dimension plays several roles depending on context.
For example, the [Time] dimension may be reused for [Order Date] and
[Ship Date]. In 2005, the role playing dimension is stored once and used
multiple times. Disk space and processing times are minimized.
...
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.developersdex.com ***