Forum Discussion
[SOLVED] - Impossible to launch Power Query Editor on a remote Postgres DB
Most of the time native connectors are preferred as they usually are faster. But I have seen cases where the native connector doesn't support custom queries - in which case you may not have a choice.
There is a bug in Power BI service. In Power BI Desktop options you can disable parallel table load to ease the pressure on your data source. But this setting is ignored in the service, and all service refreshes will still bombard your data source with parallel requests.
I have just tried to import a single table containing about 3.000 rows from my database.
Import works fine and is done in just a few seconds.
Then, I disabled the "parallel loading of tables" option.
I opened the Power Query Editor and it froze again, my computer fan speeding up so much I though my laptop was about to take-off.
Is there any limitation in the database size the Power Query Editor can handle?
I would think that as soon as I import a single small table, it only has to deal with that locally thereafter.
Or is it still communicating with the whole table in the back at launch, trying to find schemas, etc... ? I don't know what happens under the hood.
I would like to know if my problem is server, connector or size limitation related.
Many thanks