Re: Drilling down brings back incorrect numbers

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

do you have partitions or calculation around this measure?

I suffer the same issue with partitionned cube where , in fact, I have a "conflict" between 2 dimensions.
SSAS auto assign the slice of the cube for a partition, in my case I have 2 years level in 2 different dimensions, so SSAS detect correctly the partition at this level.
but I have a month of my time dimension which appeared in another year in the second dimension (sometimes the combination result in the right year, sometimes not); SSAS will produce unexpected behavior in this setup because SSAS take the aggregate value in 1 place or in the second place "randomly".
A simple refresh in the pivottable change the numbers displayed!
and forcing the slice of the cube raise an error during the aggregation process step due to the conflict.
to solve the issue in my case I have to insure that there is no conflict in the partition and slices.

"Jesse O." <jesperzz@xxxxxxxxxxx> wrote in message news:eGkSvUSXHHA.3980@xxxxxxxxxxxxxxxxxxxxxxx
I've had a weird issue when drilling down into a dimension. For the life of me I can't figure out what's going on.

The cube has two dimensions - Date and Region. Region has two levels.

For example:

When looking at the top level total, Region 1 comes back as having 15,000. However when drilling down into Region 1, the number only returns 10,000 as a total.

Where are those other 5,000? It is incorrect across the entire dimension.



.

Relevant Pages

  • Re: Drilling down brings back incorrect numbers
    ... "conflict" between 2 dimensions. ... SSAS auto assign the slice of the cube for a partition, ... in the partition and slices. ...
    (microsoft.public.sqlserver.olap)
  • Re: Cube very slow to querying when in the middle of a process
    ... Well, when incrementally updating dimensions, AS2k will automatically ... refresh the cube partitions below it which may have an impact on this. ... where you may want to have reporting OLAP cubes and processing OLAP cubes ... > Every hour we add a new partition to ...
    (microsoft.public.sqlserver.olap)
  • RE: Incrementally updated dimensions and lazy processing
    ... I would not triplicate your shared dimensions just so you can have unshared ... we have a cube containing historic ... processing the newly added month partition. ... lazy aggregation of all the cube partitions in the background. ...
    (microsoft.public.sqlserver.olap)
  • history cubes vs partitions
    ... to create a new cube for only that fact table with only ... Once the data is taken from the current table and into its history table, ... The goal is to keep the months data, and its dimensions intact. ... The idea of 1 cube with the main current partition, ...
    (microsoft.public.sqlserver.olap)
  • Re: Cube Partitions in MSAS 2005
    ... when you create a partition you have to create an SQL statement to add the ... then create a new partition, select the fact table and then modify the SQL ... the query result MUST be identical as the original table used for the cube ... have partition for each month (Time dimension is one of the dimensions ...
    (microsoft.public.sqlserver.olap)