Viewing 9 posts - 16 through 24 (of 24 total)
in SSAS, you are looking at members of a dimension and if you want to use <= operator as in SQL, you have to add up all values from the...
September 28, 2010 at 10:54 am
If the two hierarchies are essentially the same, you should not have to define another parent-child relationship. Just create another hierarchy on the same dimension with a different name
September 28, 2010 at 8:47 am
You are on the right track, and to get values for a particular time period, you have to crossjoin using the current context. Also, use DistinctCount instead of Count...
Here is...
September 28, 2010 at 8:37 am
Maybe I am missing something, but you are asking for the week 33 SUM from the cube, and that result is the same value as reported by the SQL query...
September 28, 2010 at 8:15 am
The 'link' between the fact and the dimension should be an integer, so the time dimension in your case should have a integer key in the format YYYYMMDD
September 28, 2010 at 7:55 am
What is the hierarchy structure defined on DimDate?
What does '33' refer to in the Hierarchy slice?
September 28, 2010 at 7:50 am
Great article - can you add the fact table as a resource to the example?
thanks
September 28, 2010 at 7:23 am
Thanks for sharing your story with us. I feel I am in the same position as you, except my coworker has the boss' ears and is 'senior' to me in...
December 10, 2009 at 8:41 pm
Definitely, an interesting spin would have been:
declare @STR varchar(max)
select @STR = replicate('#',10000) + replicate(cast('#' as varchar(max)),10000)+ '#' + '#' + '#'
select len(@str)
To demonstrate the fact...
October 8, 2009 at 5:47 pm
Viewing 9 posts - 16 through 24 (of 24 total)