SQL Server Connection References

Like (3) Share

Report

Posted on 6 Sep 2024 20:03:04 by CU30071738-0

Hi All,

I have a Power Platform Solution that has Power Automate flows using connection references that are pointing to on-prem sql servers.

My requirement is to move data from an on prem SQL Server (The source) and push that to 4 separate on premise SQL servers. These 4 separate servers have databases that are identical.

I created 2 connection references, 'source' and 'target'. I was thinking that I would be able to configure/update the target connection reference to point to the next server. When I make this change, it seems to corrupt all of the flows. Our only way forward seems to be, create all new flows. Am I misunderstanding how the connection references work? Does anyone have advice on how I can parameterize the target database connections?

Any advice appreciated,

Thanks,

Philip

Categories:

ALM

All responses (1)

Answers (1)

Verified answer

Michael E. Gernaey 38,707 Super User 2025 Season 1 on 07 Sep 2024 at 03:47:40

Like (1)

Report

SQL Server Connection References

Hi

A connection reference uses a Connection as its base, essentially its a pointer to a pointer.

You have to have 5 connections and 5 connection references.

because you have 5 servers, you need those 5 connections, and in your flow you use them all so 5 connection references, 1 per connection.

Not 2. Think of it this way.

A Connection has tons of details/memory/configuration etc.

the references simply make it so that in your flows and in your solutions you aren't constantly creating new connections, but instead references can be made to that Connection from anywhere and you still only need 1 connection.

Cheers,