March 2, 2010 at 6:54 am
All-
My post is related specifically to a time dimension in a cube I'm working with. I use Excel to connect to the cube, and the end users hated seeing '3/1/2010 00:00:00' as a date the data was last pulled or whatever else I used a snapshot date for. I have another field in the dimension that is formatted as a varchar to get rid of the time stamp by using a statement like convert(varchar(50),getdate(),101). What we realized as soon as the calendar year changed was that even though the dates are in order in the star schema, Analysis Services is ordering that field differently because it's a varchar. So now, 01/01/2010 appears higher than 12/15/2009, even though that order should be reversed. Since the dimension is based on a star schema, the default attribute relationships are all one to many from the key to all other attributes, and I'm having trouble configuring the dimension to sort as I need it to.
Any ideas?
March 2, 2010 at 8:49 pm
You should specify a value for the sort key of the dimension - perhaps something line CONVERT (varchar, date, 112)
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply