Reply
Frequent Visitor
Posts: 10
Registered: ‎04-05-2017
Accepted Solution

Scheduled refresh breaking with VPN secured on-premise SQL Database table

[ Edited ]

I have a Power BI Service pointing to an on-premise SQL Server Database table that belongs to a secured VLAN where I need VPN credentials to access. I have built and Enterprise Gateway to play as a bridge to the on-premise server and secure the data trasnfered. If I setup a scheduled refresh of the report in Power BI Service, and I'm in the office connected to the corporate network, everything runs smoothly. As soon as I leave the office, and my surface is not connected to the VPN, the Schedule Refresh crashes...

 

I have installed the On-premise gateway in my local machine, not in the on-premise server, that might be a valid reason to crash, isn't it?

 

Am I missing something?

 

I'm using my windows credentials hard-coded in the data source.

 

Thanks for you time!


Accepted Solutions
Moderator
Posts: 2,524
Registered: ‎03-06-2016

Re: Scheduled refresh breaking with VPN secured on-premise SQL Database table

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.

 

q5.PNG

 

 

- 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

View solution in original post


All Replies
New Contributor
Posts: 643
Registered: ‎06-24-2015

Re: Scheduled refresh breaking with VPN secured on-premise SQL Database table

hi @biswedishdevil

 

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.

Frequent Visitor
Posts: 10
Registered: ‎04-05-2017

Re: Scheduled refresh breaking with VPN secured on-premise SQL Database table

I will try as soon as I get to the office! Thanks in advance!
Frequent Visitor
Posts: 10
Registered: ‎04-05-2017

Re: Scheduled refresh breaking with VPN secured on-premise SQL Database table

I've tried applying the solution, but I find two extra problems:

- 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).

- 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.

Moderator
Posts: 2,524
Registered: ‎03-06-2016

Re: Scheduled refresh breaking with VPN secured on-premise SQL Database table

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.

 

q5.PNG

 

 

- 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

Frequent Visitor
Posts: 10
Registered: ‎04-05-2017

Re: Scheduled refresh breaking with VPN secured on-premise SQL Database table

Good morning,

 

Although the first point is solved, the second is not...

 

Let's imagine the following scenario:

 

Server 1 contains SQL Server Database A

 

Server 2 contains SQL Server Database B

 

I have a Power BI Dataset that imports data from both SQL Server Database A and SQL Server Database B, that live in different Servers.

 

Now I want to schedule data refresh, therefore I need to setup a Gateway. As far as I understood, in order to avoid VPN autentitaction, I need to install an on-premise gateway in the server where the database is located.

 

In this case, I assume I need to install a gateway in Server 1 and another gateway in Server 2, so I can reach both servers without the need of the VPN authentication. But as you said, the dataset deployed in the Power BI service cannot use more than one gateway... so, what is the solution then?