web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Installing On-Premises...
Power Automate
Answered

Installing On-Premises Data Gateway right on the SQL Production Server?

(0) ShareShare
ReportReport
Posted on by 29

According to Microsoft, it is recommend to have the data gateway installed as close as possible to the data source to minimize latency. If that is the case, I'm assuming for most people, it means the SQL server. However, I been hearing different voices where installation of the gateway on SQL produciton is not recommended. Anyone knows why this is not recommended? Anything has to do with resources/overhead? the nature of how SQL works? Or firewall/ports issues?

Categories:
I have the same question (0)
  • v-zhos-msft Profile Picture
    on at

    Hi @photonacl ,

    recommend you to install the data gateway on you computer.

    Then you can create the connections of 'SQL server' via on-premises data gateway in flow.

    Capture7.PNG

    As the document says:

    https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem

    The On-premises data gateway acts as a bridge, providing quick and secure data transfer between on-premises data (data that is not in the cloud) and the Power BI, Microsoft Flow, Logic Apps, and PowerApps services.

    Best Regards,

    Community Support Team _ Zhongys

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • photonacl Profile Picture
    29 on at

    Thank you for your reply, but I'm still not sure why it is not recommended to have the instance installed right on the server itself?

  • Verified answer
    Brad_Groux Profile Picture
    4,556 on at

    Generally speaking, it is against Microsoft best practice to install anything other than required components on a dedicated system server (SQL, Exchange, SharePoint, etc.).

     

    You can certainly install the connector directly on the SQL Server, but it is an added component that could possbily affect the performance or stability of the server - which is why they do not recommend it. For one of our clients, we installed the Gateway directly on the web front end server within their SharePoint environment without issue. Although I would have preferred to have not done so - but they didn't want to pay for another VM. 

     

    Most IT infrastructures have "tools" or "jump" servers within their environments to house small, one-off tools like the Gateway connector which is considered "best practice." 

  • photonacl Profile Picture
    29 on at

    That makes perfect sense! Thank you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 501 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 323 Moderator

#3
abm abm Profile Picture

abm abm 237 Most Valuable Professional

Last 30 days Overall leaderboard