cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
StevenWade
Level: Powered On

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
Community Support Team
Community Support Team

Re: Issues with V2 SQL Connectors?

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
Community Support Team
Community Support Team

Re: Issues with V2 SQL Connectors?

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

StevenWade
Level: Powered On

Re: Issues with V2 SQL Connectors?

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

Helpful resources

Announcements
firstImage

Power Platform Online Conference

Join us for the first ever Power Platform Online Conference!

firstImage

Coming Soon: T-shirt Design Contest

Keep your eyes open for our upcoming T-shirt design contest!

firstImage

Incoming: New and improved badges!

Look out for new contribution recognition badges coming SOON!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Top Kudoed Authors
Users online (5,957)