I have a database with 6 cubes and 2 virual cubes. This is running on
MSAS 2000.

The cubes consist of 6 different types of data, all rolled up by date.
The 2 virtual cubes roll this data into one cube (one rolls it up to a
site level, the other pulls 4 of the cubes into a line of business
virtual cube).

I have 2 time shared deminsions. The fact table for these deminsions
follows the following schema:

Row_Datetime, Year, QTR, Month, Weekending, Day

In both deminsions all levels are set to sort by key.

Year = datepart(yy,"dbo"."OLAP_TIME"."ROW_DATETIME")
Month = datepart(mm,"dbo"."OLAP_TIME"."ROW_DATETIME")
Weekending = datepart(wk,"dbo"."OLAP_TIME"."ROW_DATETIME")
Day = datepart(dd,"dbo"."OLAP_TIME"."ROW_DATETIME")

The first shared time deminsion is Year, Month, Day. The second
deminsion is Year, Weekending, Day. All 6 cubes have both deminsions
in them, as well as the 2 virtual cubes.

When I process the deminsions and browse them I see the data the way I
want to see it (sorted correctly). After reprocessing the cubes the
deminsion order changes. Specifically on the YMD (assuming data only
from July forward) the order is July, October, August, September. It
will also change the days to 1, 10, 2, 3, 4, etc.

Rather annoying.

Few things to note:
- the olap_time table has all dates from 1/1/04 - 12/31/2007.
- The 6 cubes have varying data starts. 2 cubes have data from 1/1/04,
but one didn't generate data until 7/31/05. Throughout my testing I
set all cubes to only pull data from 7/31/05. No change.

I also have a few other single cube databases that use the same
olap_time table. I followed the same key as listed above and have no
problems with the sorting of the dates.

Check this Microsoft KB article: -
http://support.microsoft.com/kb/298595/EN-US/
Hopefully that's the problem you are seeing, and installing the lates
service pack will fix it.

Dean.


"0212353" wrote:

interesting......we are running SP4.

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard
Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Check the data types on the keys/properties that you are using for
ordering. On the days at least it appears to be using string ordering.

Not sure what is up with the month level.

--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

Darren, you are correct.

The name field is a char, but the key field was a datepart from a
dbtimestamp. Switched it and it is now working properly.

Thank you!