Two same tabular cube but showing different estimated size

jennifer zen 341 Reputation points
2020-10-12T13:26:28.227+00:00

Hi,

I have two tabular cubes-> source cube and the target cube. I have made all the changes in the target cube in reference to source cube and processed it .Now both the cubes are showing different estimated size. I used BISM normalizer to compare, but all I can see the difference is in a arrangement of date dimension hierarchy as in the pic below. I assume that shouldn't be the problem right? what could be the other reasons for the difference in size? Is there any other tool/s to do good comparison as what is missing the target cube?

Thanks in advance for your help..

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,272 questions
0 comments No comments
{count} votes

Accepted answer
  1. Lukas Yu -MSFT 5,821 Reputation points
    2020-10-13T09:29:05.367+00:00

    Hi,

    How have you copied the source cube to the target cube ? Have you done synchronization ?

    And what is your main concern now ? Did the tabular models have other errors besides the size difference?


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


1 additional answer

Sort by: Most helpful
  1. jennifer zen 341 Reputation points
    2020-11-19T20:34:48.093+00:00

    Hi,

    I had to delete the cube and redeploy and process it again as I couldn't see what the issue was. This time I used synchronization as suggested to keep both the cubes same :)

    Thanks

    0 comments No comments

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.