cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
StevenWade
Advocate III
Advocate III

Issues with V2 SQL Connectors?

Previously, I've successfully built muliple Flows using the V1 SQL connectors to query and insert rows to tables in an on-premise SQL database (via on-premise gateway). The Flows using these V1 connectors (deprecated for new Flows) are still operational in our production environment.

 

This week, I had the need to build an additional Flow connecting to SQL--now using the V2 connectors. However, I can't get any of the V2 connectors to work. It exhibits as a permissioning error, but I'm using the same established SQL Server connections that are already working on our operational Flows.

 

Is there something different I need to be doing with gateway or connection configuration in order to get the V2 SQL connectors to work?
 

 screenshot.jpg

1 ACCEPTED SOLUTION

Accepted Solutions
v-litu-msft
Community Support
Community Support

Hi @StevenWade,

 

You could recreate a new connection of SQL Server connector, then try it again.

If it still has the problem, you could check the database address whether it is correct.

If you need to reference the port in the database address, you must do it with ":".

Address convention should be <server_address>:<port> and NOT <server_address>,<port>.

Source post: https://powerusers.microsoft.com/t5/Connecting-To-Data/SQL-execute-stored-procedure-V2/m-p/351327

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

View solution in original post

2 REPLIES 2
v-litu-msft
Community Support
Community Support

Hi @StevenWade,

 

You could recreate a new connection of SQL Server connector, then try it again.

If it still has the problem, you could check the database address whether it is correct.

If you need to reference the port in the database address, you must do it with ":".

Address convention should be <server_address>:<port> and NOT <server_address>,<port>.

Source post: https://powerusers.microsoft.com/t5/Connecting-To-Data/SQL-execute-stored-procedure-V2/m-p/351327

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Ok...that was the issue. Created a new connector replacing "," with ":" as the port separator, and it is working fine. Thanks!

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

May UG Leader Call Carousel 768x460.png

June User Group Leader Call

Join us on June 28 for our monthly User Group leader call!

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power Automate Designer Feedback_carousel.jpg

Help make Flow Design easier

Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!

Top Solution Authors
Users online (1,369)