Forum Discussion
Error Fetching Data for Visual in DirectQuery Mode – Need Optimization Advice
- 1 year ago
From the server hostname you shared, I guess your database is hosted in Azure.
Have you tried querying the db from any other client tool other than power bi, if yes then how long it is taking?
As you have mentioned the data load from power query to power bi is taking longer, I suggest you check the db logs and see how much time the query execution is taking. If it is not that long then I would suggest you check the network traces
Look at the network routing and see if the traffic from your machine to the db server is taking longer route or shorter route. If required leverage network watcher in Azure. Depending the results you can talk to your network team to fix the routing table.
Connect on LinkedIn
Did I answer your question? Mark my post as a solution! If I helped you, click on the Thumbs Up to give Kudos.
Proud to be a Super User!
- 1 year ago
@Hi, Mahesh0016 Just a couple of things you can try from your side:
Test the query in another tool – Try running it in SSMS or Azure Data Studio to see how long it takes. Sometimes when the server is under load, it might respond more slowly than usual. So even if it’s fast now, it’s worth checking how it behaves at different times.
Try switching to Import mode – Since the data seems to load fine in Power Query, but not in the visual, try using Import mode instead of DirectQuery. It’s a good way to test if the delay is due to live queries or something else. You might see the visual loading faster this way.
Find this helpful? ✔ Give a Kudo • Mark as Solution – help others too!
From the server hostname you shared, I guess your database is hosted in Azure.
Have you tried querying the db from any other client tool other than power bi, if yes then how long it is taking?
As you have mentioned the data load from power query to power bi is taking longer, I suggest you check the db logs and see how much time the query execution is taking. If it is not that long then I would suggest you check the network traces
Look at the network routing and see if the traffic from your machine to the db server is taking longer route or shorter route. If required leverage network watcher in Azure. Depending the results you can talk to your network team to fix the routing table.
Connect on LinkedIn
|