Forum Discussion
Understanding licencing and gateways
Tutu_in_YYC wrote:If it is local (on-premise) SQL server, the current setup is correct, just have to make sure that the computer is not turn off when the report refresh is being done. Servers usually are on 24/7.
This is what I'm not understanding - you say 'servers usually are on 24/7' as if the gateway should be running on a server. But the setup I have (which you say is correct for on-premise SQL) has Power BI and the gateway running on the user's PC. It's when the gateway is switched off that the other users cannot access the reports.
So how do I get around the problem (in the on-premise SQL server scenario) of the reports being unavailable when the user shuts down his PC (and therefore the gateway)?
So what
Super UserGateway is usually installed in the computer where the data source resides (i.e Server, but the best practice is to install in a separate 24/7 computer that has network connection to the server), not Power BI.
If your report is using Import mode, then the only time the gateway is being used is when the dataset is being refresh. Other than that, the gateway can be switched off (common for non-servers).
If your report is using Direct Query/Live Connection, then if the gateway is off, the report will not be able to retrieve the data from the data source.
So how do I get around the problem (in the on-premise SQL server scenario) of the reports being unavailable
when the user shuts down his PC (and therefore the gateway)?You option is to use import mode.
Are you using direct query or live connection?
Hi,
He's using the 'Direct' mode.
Thanks very much for the explanation. I've now got a better understanding of how things 'fit together' and so I'll be suggesting he stop using the gateway altogether and use the direct cloud connection. Hopefully it's a simple change to his existing reports so that they connect directly and not via the gateway!