3 ms·
Power Bi has been very abusive of my systems, although this has lessened of late. I can see hundreds of logins to my database per user, and when I cut the logi
by chasil 5y ago
Power Bi has been very abusive of my systems, although this has lessened of late.
I can see hundreds of logins to my database per user, and when I cut the logins per userid to 5, their applications collapse. Their queries cannot be tuned to available indexes according to my users.
They remain the very first ones that I throw off a database if there is a performance problem, with some degree of prejudice.
- go_prodev 5y agoYour users may benefit from using import mode rather than direct query mode. Under the covers Power BI is running a tabular Analysis Services Cube, so import mode will be optimized for reporting regardless of the source database indexing. The PBI dataset can be shared across users, so only 1 connection is required to update it, instead of dozens of users hitting the db directly. Also as another person mentioned, reporting is usually done on an separate database to production applications like an operational data store, data lake, or warehouse.
- mst 5y agoI've always preferred to shunt such analytics work over to a query replica dedicated to the purpose so the people doing analytics can generally only interfere with each other. Whether that's a viable answer in any given situation is of course highly variable, but even if the analytics queries are my own hand-rolled SQL it's still my preference any time it -is- viable if nothing else so I don't have to worry as much about screwing up and taking too many locks / using too few indices while I'm iterating on the query in question.