Unanswered

Won't connect to SQL

(0) Share

Report

Posted on by nghastings

Despite the plethora of information it gives you about the nature of the connection failure, I can't see this being any more straightforward. Any thoughts?

Categories:

Using connectors

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Pstork1 69,601 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Since the name is SQLExpress I assume this is an instance of SQL running on your laptop or workstation. That means its on-premises and the only way that Flow will be able to connect to it is using an on-premises gateway. But you don't have that checked. Install a gateway and try again.

Was this reply helpful? Yes No
nghastings 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes, I'm testing it on a local environment, and definitely learned this today. Unfortunately our company created accounts with an outlook.com extension, so I don't have the requisite 'work' email necessary to install the gateway.

Was this reply helpful? Yes No
Pstork1 69,601 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Are you using the Outlook.com address for Access to Flow? If so you probably wouldn't have the premium license required to install a gateway anyway.

Was this reply helpful? Yes No
v-bacao-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @nghastings ,

If you want to create an On-Premises connection, you first need to install Gateway. Please refer to Online doc for more details:

https://docs.microsoft.com/en-us/flow/gateway-manage

Then check if the license currently subscribed to the account used by MS Flow meets the requirements.

Users with a Standalone Flow license subscription can create an On-Premises connection. For example, Flow plan1/plan2.

In addition, you need to click Connect via on-premises data gateway, then edit the parameters required here, such as SQL server name and Database name.

If the authentication type you use is Windows, UserName needs to be Domin\username.

Please try again.

Best Regards,

Was this reply helpful? Yes No