The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hello
Having a view containing this command : row_number over partition results in timeout when executing the view from PowerBi. Its working fine if executed in SSMS.
I got to know from a coallegue that this is due to usage of this command which is not good for PowerBi and after a test changing the view with a table, the issue dissapears. How is possible that usable of this command in sql server view an have performance issues when executed from PowerBi?
Solved! Go to Solution.
Hi @galbo1993 ,
Generally speaking, I think most commands should be supported. What easily affects performance is the amount of data, and if you have very large data, a simple command may also cause slow queries.
Best regards,
Community Support Team Selina zhu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi @galbo1993 ,
According to your description, your connection mode is "import", first of all, for this method, you need to know that it will import the data into power bi desktop. It means the data will be loaded into power bi desktop from data source and will consume memory and disk space. Then upon load, all of the data defined by those queries will be imported into the Power BI cache. Upon building a visual within Power BI Desktop, the imported data will be queried. Therefore, if your query is complex and involves a large amount of data, it may cause a slow query and thus timeout failure for power bi desktop.
So maybe your command are too complex so that it causes timing out and failing.
If you want to get a clear picture of what's going wrong, I suggest you click “performance analyzer” , it can help you identify visuals that are impacting the performance of your reports, and identify the reason for the impact.
Or you can use “Diagnostic options”, it can help you achieve a better understanding of what Power Query is doing at authoring and at refresh time in Power BI Desktop.
Query Diagnostics - Power Query | Microsoft Docs
The above ways all can help you to check if it is a performance issues.
Best regards,
Community Support Team Selina zhu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Thankyou so much for nice response. But do you know anything specific for the mentioned command regarding more performance issues onPowerBi?
Hi @galbo1993 ,
Generally speaking, I think most commands should be supported. What easily affects performance is the amount of data, and if you have very large data, a simple command may also cause slow queries.
Best regards,
Community Support Team Selina zhu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
@galbo1993 , In can direct query it can impact the visuals display time.
In case of import mode, if can only slow download time and the visual display time
Thanks, I dont understand what do you mean, can you please describe more?
BTW, I found out its "Import"
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
21 | |
18 | |
15 | |
15 | |
14 |
User | Count |
---|---|
37 | |
33 | |
22 | |
18 | |
17 |