Share via

SSAS Cube - Data Incorrect when source is correct

Ayush Jha 1 Reputation point
2022-09-15T12:57:18.413+00:00

We have a cube which currently reads data from two separate partitions for the same measure group. By separate partitions, I mean coming from different tables. Then we have scope statements, which decides at which hierarchy level, what we show in our cube...i.e at certain level, cube shows numbers from Table_1 and at higher levels, cube shows numbers from Table_B. What is going on is, at random times after processing these partitions, I get correct number and at other times some numbers are doubling . Any reason what maybe going on? I have checked the source queries and they look good. The dimension tables look good. For example yesterday the data for July was wrong, and today the data for August is wrong.
And then on re-processing it, the data gets fixed.
It seems like for whatever reasons , we are appending to the existing data instead of replacing.
Our source is Google Big Query
Driver is CDATA Driver

The partitions are processed in batch for 3 months at a time. I.e. each batch has six partitions each month has 2 partitions, one for class and another for vendor.
Class is the one which goes bad from time to time.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,696 questions
SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,278 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alexei Stoyanovsky 3,416 Reputation points
    2022-09-16T11:26:15.107+00:00

    You got something wrong in your description. SCOPE statements are unaware of measure group partitioning, so your cube actually runs on some logic different from what you described.
    Also, you haven't really provided any proof that the source is in fact correct. You might actually run into intermittent problems with the source for all you've posted so far.
    It should be easy to check whether the data is actually duplicating by examining the sizes of partition files.

    0 comments
  2. Ayush Jha 1 Reputation point
    2022-09-16T17:06:57.81+00:00

    Hello Alexei,
    The source is correct because I captured the query at the time the cube was processed.
    The query didn't result in duplicates which we noticed in the cube.
    I didnt' see partition files.All I see is the file for the measure group with the names with suffix ".map", ".hdr" and ".data' files.
    Is there a place where we get the files at partition level?
    Thanks

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.