One of the most resource-intensive operations performed by Power BI is refreshing datasets. Each dataset can use multiple data sources, for example, your data warehouse or a SQL Server. It's important to monitor the load on these sources as well.
Even great tools have problems. Power BI is a great tool, but it is not perfect. In this article, Brent and Greg discuss some common problems and challenges in Power BI.
A guest post by Štěpán Rešl describing an approach to automated collection of Usage Metrics across many workspaces, without using the Admin APIs. This is highlighting a free solution that Štěpán has created to automate this workflow.
In Part 1, we covered options for pulling usage reports without interacting with an API. In this article, we will cover advanced techniques for pulling and storing Power BI user activity.
After a Power BI report has launched, there are some important questions. Who is actually using it? Is it reaching the intended audience? Is it being used more broadly than intended (yay!)? Or is it not being used at all (horror!)?
How do I do Version Control in Power BI? This question has been difficult to answer in the past, but is getting easier with new Power BI (and Fabric) features. Team and traditional enterprise concerns like version control have only recently received attention on the product roadmap.
A guest post by Reid Havens and Steve Campbell providing an overview of enterprise architecture features and concerns in Power BI.
A presentation about operational concerns and resources to address these in Power BI
Power BI is a SaaS product. Doesn't that mean that Microsoft handles all the operational concerns for us? Do I even need to worry about "Power BI operations" in my organization? To answer these questions, we need to understand what operational concerns are relevant to Power BI. In answering this