dbTalk Databases Forums  

datetime dimension uniquename problem (SSAS 2005)

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


Discuss datetime dimension uniquename problem (SSAS 2005) in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Bob H.
 
Posts: n/a

Default datetime dimension uniquename problem (SSAS 2005) - 05-16-2006 , 12:26 PM






I have a datetime dimension (built manually) that goes down to the day level.
The problem is that the uniquename for 12/31/2000 is 1/1/2001. Here's a
snippet of a "debugtofile" looping through the cellset:

[Time].[Year].&[2000].&[Q4 2000].&[2000]&[12]&[Dec
2000].&[2000-12-29T00:00:00]
[Time].[Year].&[2000].&[Q4 2000].&[2000]&[12]&[Dec
2000].&[2000-12-30T00:00:00]
[Time].[Year].&[2000].&[Q4 2000].&[2000]&[12]&[Dec
2000].&[2001-01-01T00:00:00]
[Time].[Year].&[2001].&[Q1 2001].&[2001]&[1]&[Jan 2001].&[2001-01-01T00:00:00]
[Time].[Year].&[2001].&[Q1 2001].&[2001]&[1]&[Jan 2001].&[2001-01-02T00:00:00]

The year 2000 is a Leap Year, but the problem does not affect the year 2004
(also a Leap Year).
The ".FormattedValue" for the member is "12/31/2000" (which is correct).
Using SQL Man. Studio to access the cube returns "12/31/2000".
The underlying dimension SQL table has the correct info in it.

The OLAP db is SSAS 2005, running on either Itanium or X64 (both exhibit the
problem), Windows 2003 Server Ent.
The front-end is Microsofts AnalysisSvcsWebCient/CubeMain.asp (minimally
updated for SSAS 2005).

Anyone have any ideas?

Thanks!
--
Bob Hodgman

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.