May 13, 2005 at 12:49 pm
I'd like a report with days across the top and 24 hours down the rows so management can compare call data performance hour to hour across days.
select
{ [TimeByMinute].[All TimeByMinute].[2005].[May].[1] : [TimeByMinute].[All TimeByMinute].[2005].[May].[10] } on columns ,
{ [TimeByMinute].[Hour].members } on rows
from ACD_Calls2
where [Measures].[Calls]
I get the "duplicate dimensions across (independant) axes" message.
Any ideas?
Richard
May 14, 2005 at 1:38 am
Yeah, it's annoying, isn't it? To get around it, I am afraid you'll need another dimension, which is pretty much the same as your 'TimeByMinute' dimension, and use that in conjuction with your existing dimension. Or, you could create a flat 'hour' dimension and use that.
If there is another way around this, PLEASE POST IT!! My cubes each have about 5 'time' dimensions to get around these problems, and that is NOT a great solution, I'm sure you'll agree.
May 14, 2005 at 7:54 am
Hey KennofromOz, Yukon help with this for a little (multi-role dims) but that doesn't help now does it
Steve.
May 14, 2005 at 5:51 pm
StevefromOzbutwannabeUS , Yukon helps with a LOT of problems we have at this client, particularly multi-role dims and especially properly 'heirarchy aware' dimensions (ie sharing aggregations etc). But, no, none of this helps now.
KennoFromOzbutsoontobeUK.
May 15, 2005 at 6:31 am
You're not looking to implement it now rather than later? You'll miss out on all the fun. Think of it as the last job you'll do in sunny weather :p
Steve.
May 17, 2005 at 1:27 pm
Thanks all! At least I know now that it wasn't just because I didn't know enough mdx. I think that's the toughest part of learning this.
Anyway, thanks for talking the time to answer.
I've got another new problem to post now...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply