Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
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
It seems like it is running the query it is evaluating, then running it again when retrieving records. Which means it is taking twice a long as it should in order to get data.
That would not make any sense, though. So what exactly is happening when Bi is evaluating a query?
Phil
Hi @psmith-nhs-inc,
What do you mean "it is taking twice a long"? Do you mean the query is executed twice? Could you provide more detailed information about your scenario? What is your data source? Is there any query reference?
Regards,
Yuliana Gu
I mean it seems like Refresh in Desktop runs every query twice. It looks like it runs it once during the "evaluation" and then again to actually load the records into the database.
My data source n this case is an ODBC connection to a MYSQL database. Under those conditions, what exactly is power BI doing when it is "evaluating" each and every query?
So no-one knows what Power Bi Desktop is doing when it says it is evaluating a 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 |
|---|---|
| 56 | |
| 47 | |
| 44 | |
| 20 | |
| 20 |
| User | Count |
|---|---|
| 73 | |
| 72 | |
| 34 | |
| 33 | |
| 31 |