Forum Discussion
Incremental Refresh with Analysis Services source
PetrP not sure why are you using import method with Analysis Service, why not use the live connection. What is the point of having AS and using import? Seems to be a strange setup.
parry2k data from AAS are modeled into an understand needs for using by report contributor. Behind the AAS model there are many sources with many diferent keys and must be "translated" to using. Of course, you can acheive that by using other techniques, but the benefits for that is using dimensions and calculated mesures on the "client/contriburo" side.
If you mentioned Live connection - there are probably the same problem - you cannot use it for incremental refresh. Or am I wrong?
Keep in mind that data in one query return f.e. 1M rows, because at each refresh must be queried all data from AAS.
I will be glad if you explain me a little more about that.
Thanks a lot!
I agree. I have a very similar setup: Analysis Services Tabular models running on premise and connected via the Gateway.
In this setup, no data goes 'across the wire' until someone tries to render a page. Then Power BI will issue the query to the source SSAS Tabular model, and only the needed result rows, properly aggregated, get returned.
If you have Azure Analysis Services, you are already paying Microsoft for the memory allocation there. Why also bog down Power BI with extra data?
Hopefully your data model is robust in its relationships, etc.
