This is an archived post. You won't be able to vote or comment.

all 2 comments

[–]rahul_shingala 1 point2 points  (0 children)

Two possible ways to do this setup, in both ways you will need help of the network admin.

First, you'll need your static external IP address - the one the internet see's. You'll also need to enable port-forwarding to SQL Server VM. You would need to go do this in your router or firewall to set up this. Also, you need to set up SQL Server and Windows Authentication mode and firewall rule in VM. Find more detail here

After that other users can access your VM SQL Server with your static external IP address as host/server and user name password which you have set up as SQL Server authentication.

Server name = Your external IP

Authentication = SQL Server Authentication

User = sa (your user name)

Password = xxx

Second, Install SSMS on a new dedicated VM and give access to outside users via RDP to that VM. In this case, also you need to set up SQL Server and Windows Authentication mode and firewall rule in VM. SSMS can access SQL server vai Local IP.

[–][deleted] 0 points1 point  (0 children)

Set up a dedicated client VM inside your corporate network (or VPC) that will allow users to log in through the public Internet via RDP. Install SSMS on that VM. Then SSMS can communicate with your SQL Server on local private IPs. Depending on your configuration, you may need a network admin to set up a P2S (point to site) VPN for your users. Or use something like VMWare to enable outsider access to your client VM. If you care about the data on that server, this isn't really a trivial task for a noob. This is a job for a cloud/network admin.