Feature request: built-in SSH tunneling

[chucker]

• SQL Operations Studio Version: 0.24.1

Steps to Reproduce:

1. Create a new server connection
2. As Server name, specify one that isn't directly reachable from your client

I've seen this offered in various other RDBMS clients such as PSequel and related admin tools such as Royal TSX, but notably not in SQL Server Management Studio.

GUI-wise, PSequel solves this with a [ ] Use SSH Tunneling checkbox that reveals the additional field SSH Host, Port, and User, as well as Identity File. Typically (but not necessarily), in this configuration, the Server name field would then be filled with localhost or similar.

Internally, you first set up an ssh connection with a client-to-server port forwarding (typically, of port 1433), then run the database connection against that forwarded port. For example:

ssh -NL 1433:localhost:1433 myUser@theRemoteServer

Here, theRemoteServer runs both SQL Server (on port 1433, but not publicly accessible) and an SSH server (on the default port 22, and accessible).

This feature's purpose is to:

• alleviate the need to manually run the above ssh command manually each time
• attach the SSH configuration to the SQL configuration

[bomb-on]

Any progress with this?

[jwhaley58]

I was really hoping with the addition of PostgreSQL that this would bubble up to the top of the list.

[dgadelha]

Handy for PostgreSQL users, it would be nice to see an update on this.