Home / Workloads / Microsoft SQL Server

How Cloudbrink's VPN Replacement works with Microsoft SQL Server

Let developers, analysts and contractors reach the SQL Server instances they need, and nothing else. Cloudbrink keeps your databases off the internet and gives each person access to specific instances, not the whole network.

Why SQL Server needs more than a VPN

SQL Server listens on TCP port 1433 by default, and attackers scan the internet for it constantly. An exposed instance invites brute-force attacks on the sa account and other logins.

A VPN closes the port, but usually gives each user the whole network. For a contractor who only needs one database, that is far more access than the job requires.

How Cloudbrink delivers SQL Server

No open database ports

SQL Server stays off the internet, with nothing listening on 1433 for scanners to find.

Access per instance

Each person reaches only the databases assigned to them.

Responsive tools

FAST edges help keep queries and management tools responsive on remote connections.

Compatibility details

WorkloadMicrosoft SQL Server
StatusTested and compatible
Default portTCP 1433

Getting started

Add your SQL Server instances in Cloudbrink

Register the database servers your team needs to reach.

Assign access to users or groups

Give each person or team access to specific instances, using your identity provider.

Connect with the Brink app

Users open their usual database tools and connect as they would in the office.

See Cloudbrink with SQL Server

We’ll show you database access over Cloudbrink on your own connections.