Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I am using the Query Editor in Power BI Desktop, with a file in "Import" mode.
I have a query "Foo", the first step of which is to pull data from a SQL Server database (= Sql.Database("SERVER", "Database", "[Query = "SELECT..."). The SQL query is very slow -- it takes several minutes to complete.
I also have query "Foo.1", the first step of which is to reference the "Foo" query (= #"Foo"). And, I believe the following also applies if I have a query "Foo.2" which appends the "Foo" query with something else.
When in the Query Editor I make modifications to the "Foo.1" query (only), then click "Close & Load", then the "Refresh" screen pops up and, for "Foo.1" only, it says "Evaluating..." for a while, then is says "Waiting for SERVER/Database..." for a while, then it loads all the rows into the data model in the PBIX file.
That is, it seems to be running my very slow SQL query against the source database. But why?! I think only the "Foo" query should run the very slow query against the source database. When modifying/refreshing downstream queries like "Foo.1" and "Foo.2" (which use reference/append/etc. to get data from "Foo"), shouldn't Power BI Desktop simply refer to the "Foo" data that is already there, already loaded into the PBIX file? Why run the very slow query against the database again?
It slows down my development effort, having to wait every time I change a downstream query. And running the query eats up a lot of resources on my server. (Oh, and it doesn't even actually refresh the data with fresh data from the database! Because I never refreshed the original "Foo" query!)
Is there some way I can prevent this, now? Or, could Power BI be "fixed" to prevent this? (Or, is this necessary for some reason that I don't see?) Thanks!
Solved! Go to Solution.
Please Check out this Article from Chris Webb's BI Blog. You can understand the logic behind this.
https://blog.crossjoin.co.uk/2016/11/20/referenced-queries-and-caching-in-power-bi-and-power-query/
Please Check out this Article from Chris Webb's BI Blog. You can understand the logic behind this.
https://blog.crossjoin.co.uk/2016/11/20/referenced-queries-and-caching-in-power-bi-and-power-query/
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |