Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi Everyone
Our organisation has changed to a case management system that finally allows us to connect via ODBC to their PostgreSQL Database.
The NpgSQL driver, unfortunately kept complaining about insufficient certificates.
Therefore I am using the PostgreSQL driver from https://www.postgresql.org/ftp/odbc/versions/msi/
I am able to create reports in PBI by I importing one table at a time - howevere, talking to our CMS provider they have limited the connections to 4 at a time.
My data model has 15 tables and as far as I can tell every table uses one connection.
I was wondering if PowerBI is capable of closing connections before opening a new one? Is it something that I can manipulate in my connection string? - If neither of these are an option, what would you recommend as a solution?
Solved! Go to Solution.
Hi @Daniel_LP ,
More details will be more helpful.
Do you have any error mesage in Power BI Desktop? If you have, please share the screenshot of the error message.
In addition, you could use SQL Server Profiler to trace if every table uses one connection.
Finally, I'm afraid that PowerBI cannot close connections before opening a new one.
You may could try to enable this option under Data Load.
Best Regards,
Cherry
Hi @Daniel_LP ,
More details will be more helpful.
Do you have any error mesage in Power BI Desktop? If you have, please share the screenshot of the error message.
In addition, you could use SQL Server Profiler to trace if every table uses one connection.
Finally, I'm afraid that PowerBI cannot close connections before opening a new one.
You may could try to enable this option under Data Load.
Best Regards,
Cherry
Hi Cherry!
Thank you very much!
Turning off "Parallel loading of tables" has fixed the issue for me!
Thanks
Daniel
Check out the July 2025 Power BI update to learn about new features.