Multiple joins to the same underlying table

#1

I have a cube which has 7 different time dimensions. For each time dimension
I have created a separate view: e.g. vwTime1, vwTime2, vwTime3, etc...

In my fact table I have Date1, Date2, Date3, etc... which join to their
respective Time views. This cube is taking a VERY Long time to process and
I've tracked down the problem to the 7 joins from the fact table to the Time
table based on the results from running an "Estimated Execution Plan" in
Query Analyzer. Does anyone have any advice on how to optimize or reduce the
number of joins to the time table?

#2

You can also create a hierarchy for all the time dimensions, so that they
share their aggregations

Rolando

"Jéjé" <willgart (AT) AAAhotmailBBB (DOT) com> wrote

Quote:

have try to optimize your cube?
otimizing a cube remove some joins , but you have to make sure that all
the
date1,2,3... exists in each dimension.
the join used by default is here to insure that the loaded fact table
contains only known dimension member.

before optimizing your cube, you have to insure that the lowest level of
the
dimension is unique (member key must be unique)

you can optimize manually by changing the column used at the lowest level
of
the dimension in the cube. change the column used from the vwTime1 table
to
the fact.date1 column. this step remove the join because you no longer
need
it. (the opitmize cube do this for you automatically)

"Matt" <Matt (AT) discussions (DOT) microsoft.com> wrote in message
news:4615B8EE-1EFE-4E2B-A523-2A0ABB8BF480 (AT) microsoft (DOT) com...
I have a cube which has 7 different time dimensions. For each time
dimension
I have created a separate view: e.g. vwTime1, vwTime2, vwTime3, etc...

In my fact table I have Date1, Date2, Date3, etc... which join to their
respective Time views. This cube is taking a VERY Long time to process
and
I've tracked down the problem to the 7 joins from the fact table to the
Time
table based on the results from running an "Estimated Execution Plan" in
Query Analyzer. Does anyone have any advice on how to optimize or
reduce
the
number of joins to the time table?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Multiple joins to the same underlying table

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap

Multiple joins to the same underlying table - 09-08-2005 , 11:09 AM

Re: Multiple joins to the same underlying table - 09-20-2005 , 11:20 AM