There is no fixed capacity per Pro user. That's why it is called SHARED. It depends on how much users are using Power BI Service with shared capacity.
As per my feeling usually, it is around 3-5 GB.
Remove not used columns in data load. It means if you want to load Clients table, then prepare view/table on database side with needed fields. (Or while connecting to DB write SQL script where choose required columns).
Reduce the number of rows in a way I told step before (smaller period or any other filters, if possible).
Sometimes better if you will do maximum SQL JOINes on database side then on Power BI side.
There are several logs you can collect for the gateway, and you should always start with the logs. The simplest way to collect logs after installing the gateway is through the user interface. In theOn-premises data gatewayuser interface, selectDiagnosticsand then select theExport logslink near the bottom of the page, as shown in the following image.
%localappdata%\Microsoft\On-premises Data Gateway\GatewayConfigurator*.log
On-premises data gateway service logs
C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log
TheOn-premises data gateway serviceevent logs are present underApplication and Services Logs.
Fiddleris a free tool from Telerik that monitors HTTP traffic. You can see the back and forth with the Power BI service from the client machine. This may show errors and other related information.
When using the gateway for scheduled refresh,Refresh Historycan help you see what errors have occurred, as well as provide useful data if you should need to create a support request. You can view both scheduled, as well as on demand, refreshes. Here is how you can get to theRefresh History.
In the Power BI navigation pane, inDatasets, select a dataset > Open Menu >Schedule Refresh.
InSettings for...>Schedule Refresh, selectRefresh History.
Connected with gateway (not personal mode) and no pb with id informations. The datas come from Dynamics NAV. And I got no pb when I refresh the report with PBI Desktop! (use 15Go/32Go of memory system)
As I said, I got no pb with the others reports (same gateway, same db...).
The maximum size for datasets imported into the Power BI service is 1 GB. These datasets are heavily compressed to ensure high performance. In addition, in shared capacity, the service places a limit on the amount of uncompressed data that is processed during refresh to 10 GB. This limit accounts for the compression, and therefore is much higher than 1 GB. Datasets in Power BI Premium are not subject to this limit. If refresh in the Power BI service fails for this reason, please reduce the amount of data being imported to Power BI and try again.
Community Support Team _ Xiaoxin Sheng If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
For learning resources/Release notes, please visit: | |
Power BI Desktop mainly consists of two applications:
Power BI Desktop (UI and back-end)
MS SQL Server Analysis Services
Main calculations are done by the second one.
You can check memory RAM using Windows task manager and Resource Monitor by tracking msmdsrv.exe:
If PBIX file size is 300MB. The same size it will have in Power BI Service (what we can see in your screenshot). But it is just compressed size. When you do refresh the report then it can take up to 20GB for instance. In that case, it is using RAM. When you have just Power BI Free/Pro without Embedded/Premium capacity then you use capacity shared with all other users.
The issue here that your report is using11 GB while refreshing. That means you need to buy additional memory (capacity, as I mentioned earlier) and your report will not refresh without it because of a huge amount of data.
If you not willing to do so, you need to optimize your Power BI report data model. Can you share a screenshot of it?