Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
I have a Power BI Report with four (4) tabs, each of which has its own SQL statement to pull its data. All four SQL statements use Import, not Direct Query. I published it to Power BI Online, all good. I then published each page of the report to a single Dashboard in Power BI Online - again, all good.
I then published it to a Dynamics 365 dashboard, with each page (tab) being a separate tile on the dashboard. Great. That all works nicely...except. Whenever you make a selection in one of the slicers, it takes literally minutes to refresh.
Why is this? I thought the whole point with using Import rather than Direct Query is that it caches a local copy, so that refreshing the display is very quick. But that's not what I'm seeing. Have I done something wrong in how I've published it? I've not had this problem before, but none of the other visuals I've published have been anywhere near this big (all before have used a single SQL query).
Solved! Go to Solution.
Hi @Budfudder,
As the blog I shared you mentioned, though DirectQuery is performing much slower than the Import Data option, there are still many factors will affect the speed for loading data.
Import Data loads data into memory. It is always faster to query data from memory (Import Data), rather than querying it from disk (DirectQuery). However, to answer the question that how much faster it is, we need to know more details about the implementation. Depends on the size of data, specification of the server that the database is running on it, the network connection speed, and factors such as is there any database optimization applied on the data source, the answer might be entirely different.
Best Regards,
Cherry
Hi @Budfudder,
I thought the whole point with using Import rather than Direct Query is that it caches a local copy, so that refreshing the display is very quick. But that's not what I'm seeing. Have I done something wrong in how I've published it? I've not had this problem before, but none of the other visuals I've published have been anywhere near this big (all before have used a single SQL query).
To some extent, your understanding is correct. However, to answer the question that how much faster it is, we need to know more details about the implementation.
You could have a reference of the Performance in this blog. You should choose the right connection based on your data size.
Best Regards,
Cherry
Thanks, Cherry. Unfortunately some of the DAX I'm using in the report can't be used with Direct Query, so I had to go with Import. I don't understand why it's taking so long to load given that I'm using Import.
Hi @Budfudder,
As the blog I shared you mentioned, though DirectQuery is performing much slower than the Import Data option, there are still many factors will affect the speed for loading data.
Import Data loads data into memory. It is always faster to query data from memory (Import Data), rather than querying it from disk (DirectQuery). However, to answer the question that how much faster it is, we need to know more details about the implementation. Depends on the size of data, specification of the server that the database is running on it, the network connection speed, and factors such as is there any database optimization applied on the data source, the answer might be entirely different.
Best Regards,
Cherry
User | Count |
---|---|
141 | |
113 | |
104 | |
78 | |
64 |
User | Count |
---|---|
136 | |
125 | |
107 | |
70 | |
61 |