Forum Discussion
gateway can solved firewall error?
Yes on-premises gateway will mak it more stable and may help you in speed up processing too.
You can install your enterprise gateway on the same server as the datasource but keep a note on the ports that are required to be opened on the server to make the gateway work as it needs to communicate outside. If your report is already published in a workspace you don't have to do anything, just create a gateway and register it then you will see an option to ocnnect your datasource to gateway and just add it there.
You can find more details here:
https://docs.microsoft.com/en-us/data-integration/gateway/service-gateway-communication
https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-indepth
You need to review your machine specs where you have to install the gateway, also its not required for gateway to be installed on same server as your data source, it just needs to have connectivity with your data source and other ports as mentioned in the link that I shared above.
Risk is this only if your gateway consumes too much memory then it might impact other systems hosted on same machine so its advisble to have on a separate server. You don't need to download PowerBI desktop on your datasource as you just need to create your report and then you just publish it to Service and source can be added there directly on gateway.
nitishsh91 So i downloaded Enterprise GW on the same machine as my source ( i have no other option), from refresh that takes 4-5 hours - now the refresh in service is 7 minutes! (too good to be true)
But i just install the GW, with no specific ports and other advanced settings, im just want to be sure that in the future the GW will not casue any errors to my source, but from 5 hours to 7 minutes is Amazing!
"gateway consumes too much memory then it might impact other systems" - Do you mean RAM or CPU while refreshing ?
Thank you!
That sounds great.
On-premises gateway only consumes a lot of memory when you are freshing too many reports at the same time and doing a lot of aggregationg in reports otherwise it should be fine, though MS recommends below: