"0 aggregations were designed" issue

  • i'm having trouble processing a cube. it has 3 parent child dimensions (each one a sqlserver view).  prior to processing, when i go through the storage designer, regardless of design option (size, %, or manual), it comes back and says "0 aggregations were designed".  2 of the 3 dimensions have the "show all" level removed, and there's no problem.  when i remove the "show all" level from the 3rd dimension, i get the 0 aggs message from the storage designer.  if i leave the "show all" level on for that dimension, all is fine.  has anyone else encountered this?  is this some sort of limitation i've got to deal with?  any help would be appreciated.

  • This was removed by the editor as SPAM

  • Do any of your dimensions have customized key properties?  I ran into an issue where I customized the name and keys, but the calculations incorporated a parsing error that generated equivalent null keys...  Null keys = no aggregation...

  • no they don't.  my parent child dimensions all show the top level now, and when this is the case, the 0 aggs problem goes away.   i guess in my newbieness, i had thought that i could get away with not having an "unspecified" or "inactive" value in the dimension to assign rows in the fact table to when that row didn't apply to a particular place in the parent / child dimension.  prior to that i had all kinds of null key messages happening.  now that i've added that "unspecified" placeholder in the dimension, it kind of makes sense that i need to see the top all level for each dimension.  so, i'm not sure if that's a workaround or a solution, but that's what i ended up doing.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply