Forum Discussion
Scheduled refresh breaking with VPN secured on-premise SQL Database table
- 9 years ago
Hi biswedishdevil,
- When I want to setup the scheduled refresh to use the new gateway I can't select the new one. (although if I go to Manage gateways I've setup the datasource and it's online).
Assume the dataset only have one SQL Server data source, and you have created the SQL server data source use the same connection information and credential as in desktop under two data gateways, those two gateways should be available for this dataset.
- What happens when the dataset i've created have two source tables that come from two different servers? As I far as I know, I can only use 1 gateway for each dataset scheduled refresh.
Assume the dataset have two SQL Server data sources, we must create two SQL Server data sources use the same connection information and credential under the same data gateway. If those two data sources are created under different data gateways, the dataset can't be configured to use data gateway.
Best Regards,
Qiuyun Yu
The scenario you described is exactly what I would expect to happen.
I would assume that as soon as you are off your network, which also means you are no longer connected using the VPN, the Gateway can no longer get the required access to the SQL Database. And when that happens the Refresh will fail.
I would suggest if possible to install and configure the Gateway to run on a server inside your network. This would then mean the VPN is no longer required. As well as then the refreshing would happen as per the schedule.