Forum Discussion
Import SSAS Tabular Database: Unexpected Exception
Thanks for the feedback. We've attempted several memory settings but none resolved the issue.
However, after futher experiments we've made some discoveries. So our case was as follows: We have a source database that is modeled as a Star Schema. Furthermore, we've created a SSAS Tabular cube for this database and then tried to Import this SSAS Tabular Cube into Power BI. After creating the connection in Power BI Desktop to this SSAS Tabular cube we go to the Navigator window in Power BI that allows the user to pick from a list of tables. What we have noticted is that as we selected tables from the left hand side of the window, on the right hand side in the preview we can see that the data is displayed as a cross-product of all the rows in all the tables that have been selected. And as we select more tables the error mentioned above comes up. I am not sure why this cross-product takes place but as you can imagine what is in the preview becomes very huge very quickly and this is likely why the error comes up.
So our understanding is that anything imported into Power BI Desktop will be converted into a Tabular Model so it seemed counter intuitive to take an SSAS cube that is already in Tabular mode and have Power BI Desktop convert it to a Tabular Model again. Perhaps it is not best practice to do that in such a scenario.
So instead we did an Import directly from the source database (the star schema instead of our SSAS Tabular) and that worked. Also in that case, as we selected the list of tables to import (from the Navigator window) we did not see any cross-product taking place. The Navigator in this case was simply showing the contents of each table selected.
This has to be a bug, right? There is no logical reason for the behavior to be a cross product. Import should either separate the tables selected into distinct tables in Power BI or it should create a results set based on the Tabular model.
- Anonymous7 years agoNot applicable
I can't confirm it's a bug but it sure sounds like one.