Karin Grünauer on 21 Jun 2016 19:31:49
As we have found out, when the user runs a PBI report connected to SSAS and gradually clicks on different slicers or tabs of the report, new queries are continuously launched, without cancelling the previously started ones. A user can select slicers asynchronously without waiting for previous actions/queries to be completed, and continously start new and new queries. When new slicers are selected, this should cancel the previously started queries (because parameters have meanwhile changed and they are no more relevant), however they continue running. Even one user can easily "kill" the server by such clicking on slicers and tabs, not even talking about tens or even hundreds of users.
After a while, this leads to an enormous amount of queries running at the same time, consuming a lot of server resources and effectively blocking the server to process new queries. This becomes a huge problem especially when more users are running PBI reports at the same time.
Thank you very much for your help and support!
- Comments (5)
RE: Add possibility to cancel queries in Power BI Service
Yes this issue is very important - come on MSFT this should be basic tablestakes!
RE: Add possibility to cancel queries in Power BI Service
Come on guys... this is a show stopper
RE: Add possibility to cancel queries in Power BI Service
This was added to Power BI Desktop in May 2019, but not into the service.
Please add it into the service, it's killing us on large models
RE: Add possibility to cancel queries in Power BI Service
From 2016... how is this not fixed?? Or at least commented on from someone at Microsoft?? This affects all gateway directqueries, not just SSAS. We're seeing this at various clients too causing them to pause Power BI evaluations. Please get this very fundamental feature implemented!
RE: Add possibility to cancel queries in Power BI Service
I can't even begin to say how impactful this simple change would be to the stability of backend data sources such as SSAS cubes when Power BI is hammering them with queries which the user has already "cancelled" by changing the slicers. Please actually cancel the old queries when a slicer is changed!