Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago

[SOLVED] - Impossible to launch Power Query Editor on a remote Postgres DB

Hi fellow PB users,   I am working on my company's ERP database which is on a remote server hosted by a cloud provider. I connect to it via an ODBC connector, because direct connection to Postgres...
Need Help
Anonymous's avatar
Anonymous
Not applicable
4 years ago

Hi Ibendlin,

 

Thanks for taking the time to read my message and reply!

 

Yes, it stills locks up even with a single table.

Well, I connect via an ODBC connector to my database and import only one table, a small one of 50 lines just to try.

And I am still unable to access the Power Query Editor. It just freezes PBI after minutes of trying to load unsuccessfully.

 

What is the "enable parallel load of tables" issue exactly?

Could this problem be linked with the type of connector I use? 

Do you think I would have more success with a direct Postgres connector in PBI? (if I ever manage to solve my certificate problem but that's another subject)

 

Regards

 

Antoine

lbendlin's avatar
lbendlin
Super User
4 years ago

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.

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    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