Custom Hybrid Connection Manager

Santhi Dhanuskodi 145

Hi,

I would like to know if we can have a custom hybrid connection manager in .net core code. I would like to connect to on-prem sql server from a cloud deployed .net solution. I am using Azure app service /Relay/Hybrid Connection for the same. I would like to know if we can write a custom hybrid connection code in the .net solution itself.

If yes, please share links and documentation.

Grmacjon-MSFT 16,446 Reputation points

2024-05-15T22:12:04.9466667+00:00

@Santhi Dhanuskodi checking to see if the below response help answer your question. Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution. Thanks

1 answer

Bruce (SqlWork.com) 57,646 Reputation points

2024-05-08T15:49:56.0533333+00:00

your goal is not clear.

the relay/hybrid is typical proxy application with two components. the azure server proxy, and the on-premise proxy client. the proxy client connects to the azure server so, that no inbound connection is required. the sql client code, just connects to the proxy, which behaves just like a direct connection to the sql sever

if you reversed engineered the proxy protocol the you could implement the server code in your application. this would require your site have an additional ipaddress for the proxy connection to on-prem, so you'd have to use a VM to host your site. this additional ipaddress is what sql client code would connect to.

instead of reverse engineer, it would probably be easier to just write you own proxy server and client. As sql client does not support http, the proxy code would need to be hosted by a VM to support raw tcp traffic.
Please sign in to rate this answer.

1 person found this answer helpful.
Santhi Dhanuskodi 145 Reputation points

2024-05-08T16:00:08.8766667+00:00

My goal is to connect to on-prem sql server from cloud hosted.net application without using Azure Relay/Hybrid Connection. I am looking for options to implement it .net solution itself.

Bruce (SqlWork.com) 57,646 Reputation points

2024-05-09T15:48:05.7933333+00:00

you have a couple options:

the easiest solution is to create a on-prem webapi to SqlServer and expose to the internet.

if you don't have internet access than the next easiest is to create a signal/r api to your database. use azure for the hub, and create an on-prem signal/r client to respond to database requests.

next is hosting a web socket application in azure, and a on-prem signal/r client. define a steaming protocol to call SqlServer.

write you own tcp/ip proxy. this involves a azure server (probably hosted by a VM to get good control of the tcp traffic) and a on-prem client. the on-prem client opens a persistent connection to the azure server. google for sample code (most are forward only, you will need to add the client connect and double forward).

install an azure vpn gateway, which is a hardware solution.

note: if your underlying cause is a flaky network from the on-prem client to azure, or the on-prem client to sqlserver, then you will face similar issues.

Andrew Sutton 0 Reputation points

2024-05-16T10:07:17.31+00:00

The goal is to use the existing Azure Relay Hybrid connection functionality with a custom proxy and client so that Hybrid connections can be used without an App Service. This would then allow integration with other compute resources such as AKS
Sign in to comment

Share via

Custom Hybrid Connection Manager

1 answer