Forum Discussion

hashtag_pete's avatar
hashtag_pete
Helper V
3 years ago
Solved

Gateway for SQL Server and oData (on prem)

Hello all,    I have the following set-up:  we are using Business Central (on prem). For most tables, I use the "Business Central (on prem)" oData connector.  For large tables, I use the SQL Ser...
  • hashtag_pete's avatar
    3 years ago

    Hello, 

     

    I contacted the Power BI support team regarging this issue and the following procedure solved the issue:

     

    When setting up the SQL connection, I entered the IP address XXX.XX.XX.XX - the solution was, to simply change this to the domain name of the server. 

    As a reason, I will copy this answer from PBI support team here (I'm no DBA or something, so this doesn't mean a lot to me):

    We discussed this issue with our internal team, we found two scenarios causing this issue; firstly you are using any other IP address not the VPN to connect with the gateway. Secondly, You need to add your Power BI Gateway server IP in your Azure SQL firewall rule. Below is the document for your reference.
    IP firewall rules - Azure SQL Database and Azure Synapse Analytics | Microsoft Learn
    We suspect that, any one of these scenario causes the issue here in configuring the gateway in power bi. Whenever you tried with IP address make sure it should be "Public".

    I am pretty sure that I entered the correct IP address (as it worked in stand-alone mode as well) so not quite sure what they want to tell me with the first possibility, but as I have a running refresh now, I am happy 🙂

     

    Best

    hashtag_pete