Forum Discussion
Import data from SSAS Tabular model
Have you managed to fix the issue? I am facing the same problem! Using Direct Query on AAS I can get the separate tables the way I have defined them in Analysis Services, whereas importing results in one big table with all the measures and dimensions into one :o Big mess!
No, I haven't gotten the solution. Sorry.
- Anonymous8 years agoNot applicable
I think I may have found a workaround. You connect to AS and when you can choose which tables to load, you only choose one table. You load it (or edit first and then load) and then you connect again to AS via Get Data and choose another table, and so on, until all the tables needed are imported.
But for my case, I think DirectQuery is the better connection option.
Hope this helps!
- Shelley5 years agoPost Prodigy
Anonymous Thanks for the help! I like your workaround comment. Helped me a lot!
- Anonymous5 years agoNot applicable
Shelley since my comment, there has been quite a lot of Power BI advancements, so I do not see the need to import from AAS model anymore. We wanted to import so that we can add more data sources directly in the Power BI desktop model. But the new composite models feature that works with AAS models is fixing this issue. An extra note Shelley, opening to import for users can put big strains on your AAS Server when they refresh the data (and you have no control over this), so it can disrupt your normal DQ model. I am unsure what your case is, but I would advise against using import on AAS models
- Anonymous8 years agoNot applicable
Anonymous Thank you. We currently are using the "Import connections & scheduled refresh" from SQL Server.
"Query performance" is more important than "realtime data" to us.
Originally, we try to design the model in SSAS Tabular due to the consideration of central management of those created measures for different reports.
We will keep trying it. Thank you!
- Anonymous7 years agoNot applicable
I know this is an old post, but it sounds like you need to establish relationships between your tables. You will only ever have one Model.bim file by the way; this is not affected by the number of tables you import. If you haven't done so, click on the Diagram icon (highlighted in the screen snip below) and establish those relationships.