Skip to main content
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Not applicable

Power BI desktop keep loading connection to model after changes in datamodel

Hi guys,


I hope you guys can help me!

I have made a connection with an on-premises postgresql database using a gateway on a virtual machine.

The connection succeeded and I can load the tables of the database and use incremental refresh in the Power BI service.

After transforming the datamodel like removing columns in a table, I apply the changes in Power BI desktop.

But when applying, the model keeps loading on "Creating connection to model". Its realy weird because if i don't transform data the connection succeeds and I can visualize my data.


So, does somebody now how I can solve this problem? I don't think the size of the model is causing it, because when I add one small table to the model, I get the same problem......


Kind regards,




Super User
Super User

Hi @Anonymous 


It sounds like you may be running into an issue with the Power BI Desktop model exceeding the maximum size limit for the on-premises data gateway. The maximum size limit for a Power BI model that can be loaded through the on-premises data gateway is 2 GB.

To confirm if this is the issue, you can try the following:

  1. Check the size of your Power BI Desktop model by going to File > Options and settings > Options > Data Load > Query Diagnostics.

  2. If the size of your model is greater than 2 GB, then you will need to reduce the size of your model to be able to load it through the on-premises data gateway. You can do this by removing unneeded columns, tables, and measures, or by reducing the amount of data loaded into the model.

  3. Another solution could be to split the model into smaller chunks, and refresh them separately.

  4. If you're still facing the issue, try to clear the Power BI cache, as it might be possible that the issue is caused by corrupt cache data.

  5. If none of the above solutions work, it could be an issue with the on-premises data gateway. You can check the gateway's log files for any error messages, or try restarting the gateway to see if that resolves the issue.

Keep in mind that the performance of the gateway might be affected by the complexity of the model, so try to simplify the model as much as possible.


If this post helps, please consider accepting it as the solution to help the other members find it more quickly.

Appreciate your Kudos!! 


LinkedIn | Twitter | Blog | YouTube 

Helpful resources

Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

Power BI Carousel June 2024

Power BI Monthly Update - June 2024

Check out the June 2024 Power BI update to learn about new features.

RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.