Forum Discussion
Loading Large Tables
Hey Budfudder,
I think the best practice for loading large datasets is using the Direct Query method instead of Import.
Also, are you running on a 32-bit or 64-bit machine? And do you have atleast 8GB of RAM?
I would also recommend looking at your current Connection Timeout configuration.
Cheers,
Alan
- Budfudder9 years ago
Helper IV
I'm running Windows 10 64-bit, with 8GB of RAM.
I'm using the Direct Query method, not Import.My mistake - we are using Import, we have no choice - Direct Query for postgresql is not supported.I'm unable to find the Connection Timeout configuration - where is it?
- tringuyenminh929 years ago
Memorable Member
Hi Budfudder,
Does your postgre database store in this computer? Is this error from database side? With DirectQuery, each chart just loads maximum 1 mil rows when you interactive( https://powerbi.microsoft.com/en-us/documentation/powerbi-desktop-use-directquery) so I don't think it's problem from PBI.- Budfudder9 years ago
Helper IV
Unfortunately (from what I can see) postgresql isn't one of the databases supported by DirectQuery - so I can ONLY import. Does importing actually create a copy of the whole table locally?
I've had similar problems connecting to our CRM database (not timeouts or failures, but just HUGE load times) - again, it's not supported by DirectQuery.