Forum Discussion
Power Query Preview (Auto-Sorting?!?!)
In the initial connection screen robarivas you can write your own SQL statement. I activily recommend against this in production as it will break 100% of all future query folding. But in this scenario, it can assist in trouble shooting.
Does it do this with any table on that server, or just this one? if it just this one, it might be an insanely massive table and the driver isn't coping with it well. If that is the case, consider working with your DBA to privide a view to you to use vs the table. Then connect to the view. All transformation later that Power Query can convert to SQL statements will fold.
If it is all tables though, then there is definitely a problem with the server configuration or your driver (ensure you have the latest Oracle driver for Power BI.)
Great robarivas - glad you are at least able to see some data. Can you mark one of these as the solution so this thread can be marked as solved - at least for this minor mystery?
Be sure to get a view, or add a filter in your SQL statement. Otherwise, when this loads, Power Query will read all 250,000,000 records before doing transformations as it will not be able to fold any other steps since you hardcoded the connection query.
Thanks edhans I'll mark one as a solution as a favor to you for helping out and because I think this issue (if its really on my side) can't be addressed by the Community. But in actuality I feel this is very unresolved. Until I can be shown (like by a DBA on my side perhaps) that the database and/or its driver have some kind of configuration problem, I won't see this issue as resoved. Nowhere in any Power Query documentation, articles, books, etc. have I seen a requirement or recommendation that views and/or hand-written SQL be used. I'd say I've probably only ever seen the opposite recommendation.
I fully understand and can appreciate your issue robarivas - and you are right. Avoid native SQL where possible. Put it in a View on the server, or use Power Query for all transformations.
But again, I've been on these boards for a few years and while I have obviously not seen every post, I've not seen this issue before, and we know that there are people using Power BI and Power Query with tables much larger than what you have and are not getting these time out issues. So it seems to me to be resolved in that, barring other people coming in and going "Yeah, same with me and my Oracle database" this isn't a bug in Power Query, nor a design flaw, but something with your database or this specific table.