Forum Discussion
Query change keeps spinning on OK button.
I have a couple of oracle sql queries that I have been using without too much trouble. But, when I go make a change, it's been taking longer and longer to come back from the Power Query. I've tried to create a new desktop app with just one of the queries, and it will take hours to come back... whereas before it had taken 15 mins or so.
At this point, it's not even getting to the preview in a quick timeframe, let along the evaluation and the pull of data.
Any ideas of what's going on?
how can i resolve this?
I've tried rebooting, etc...
This is pretty frustrating
fyi - i'm using an oledb connector to oracle.
the query isn't the prettiest in the world, but it had been running much faster
5 Replies
Hi Anonymous .
In general I would recommend doing filtering in the SQL Query itself, it will save you time in processing. Also, I would recommend running query diagnostic on your steps in Power Query. You can find it in Power Query -> Tools -> Start Diagnostic. It will tell you how much time a step takes. Let me know if it helps.
Thanks,
Abhinav
If you have not tried clearing Cache, try this by going into Options and see if it helps.
i did that... it doesn't seem to have helped. i can hit cancel
and, save / close... it goes into the validation part
however that's taking a long time as well (hours)
which doesn't make any sense. I'm not sure how i can reduce the number of rows, without having to go back and change it to original number... and having it result in the same problem
Hi Anonymous
AnushaSri AbhinavJoshi Thank you for your reply!
Please allow me to provide some other insights:
-
OLEDB Connector Settings: Ensure that you're using the latest version of the Microsoft OLE DB Driver for SQL Server, as it's crucial for optimal performance and compatibility. You can download the latest version from here: Microsoft OLE DB Driver for SQL Server - OLE DB Driver for SQL Server | Microsoft Learn.
-
Network and Database Performance: Sometimes, the issue might not be with the query or Power BI itself but with the network or the database server's performance. If possible, check the database server's load and ensure there's no network bottleneck affecting the data transfer.
Best Regards,
Jayleny
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
-
