*Cube-Host– full cloud services!!

get a consultation

Installing MS SQL Server on Windows VPS

This guide walks you through a clean SQL Server 2019/2022 installation on a Windows VPS, with practical best practices: disk layout (data/log/backup), service accounts, tempdb planning, network access (TCP/IP + port), firewall rules, and post-install validation.

For stable SQL performance, choose a reliable Windows VPS and consider plans from our VPS hosting lineup that offer enough RAM and fast storage for database workloads.

What You Will Need

Windows VPS (recommended: separate disk for SQL data and backups if possible).
Local/Domain Administrator rights.
SQL Server 2019/2022 distribution (ISO/installer).
(Recommended) Dedicated service accounts for SQL services (domain / gMSA / MSA when available).

Practical sizing note: SQL Server is memory- and I/O-sensitive. For production workloads, prioritize RAM and storage latency over raw CPU cores.

Before Installing: Plan Disks and Directories

A common best practice is to separate directories (ideally different volumes):

Data: D:\SQLData
Logs: E:\SQLLogs
Backups: F:\SQLBackups
TempDB (optional): T:\TempDB

Create directories (edit drive letters to match your VPS):

New-Item -ItemType Directory -Path D:\SQLData -Force
New-Item -ItemType Directory -Path E:\SQLLogs -Force
New-Item -ItemType Directory -Path F:\SQLBackups -Force

After installation, grant NTFS rights to the SQL Server service account(s) on these folders if you use custom accounts. (Many installs use virtual accounts by default; permissions are typically handled by setup.)

Running the Installer

Mount/open the SQL Server ISO → run setup.exe → Installation → New SQL Server stand-alone installation.

Components (Feature Selection)

Minimum for most servers: Database Engine Services. Add features only if you really need them (Replication, Full-Text, SSIS, etc.). Keeping the footprint small reduces complexity and attack surface.

Instance Configuration

Choose:

Default instance (MSSQLSERVER) — simplest for most cases.
Named instance (e.g., DEV) — useful if you run multiple SQL instances on one VPS.

Services and Collation (Service Accounts / Collation)

Service accounts: prefer dedicated accounts (domain/gMSA) for production. Set SQL Server Agent to Automatic if you plan scheduled jobs/backups.
Collation: choose what matches your application requirements. Do not change collation casually after deployment.

The installer may offer Grant Perform Volume Maintenance Task — this enables Instant File Initialization (IFI), which can speed up data file creation/growth. IFI is commonly used in production, but follow your security policy (it can expose remnants of previously deleted data on the same volume until overwritten).

Database Engine Configuration

Authentication mode and administrators

Prefer Windows Authentication when possible. If your application requires it, you can enable Mixed Mode (Windows + SQL logins). If Mixed Mode is enabled, set a strong sa password and limit its usage.

Data / log / backup directories

Point SQL Server to your planned directories (data, logs, backups). This helps performance and simplifies maintenance/backup routines.

TempDB planning

TempDB performance affects many workloads. A common starting point:

Up to 8 logical CPUs: start with the same number of TempDB data files as CPUs.
More than 8 logical CPUs: start with 8 data files and increase only if monitoring shows contention.
Use equal file sizes and consistent growth settings.

Finish Installation and Install SSMS

Complete the setup wizard. For management, install SQL Server Management Studio (SSMS) on the VPS or on your admin workstation and connect remotely.

Enable Network Access (TCP/IP) and Set a Static Port

Open SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for your instance → enable TCP/IP.

Set a static port (commonly 1433, or a custom port) in TCP/IP properties → IP Addresses tab → IPAll section:

Clear TCP Dynamic Ports (leave empty)
Set TCP Port to your chosen value

Restart the SQL Server service for changes to apply:

Note: If you keep dynamic ports (often on named instances), clients may require SQL Server Browser service (UDP/1434). For most production deployments, a static port is simpler and easier to firewall.

Windows Firewall Rules

Allow inbound connections to your SQL Server TCP port. If you use SQL Browser for dynamic ports, allow UDP/1434 (only if truly needed).

Example PowerShell rules (replace port and optionally restrict by RemoteAddress):

# Replace 1433 if you use a custom port
New-NetFirewallRule -DisplayName "SQL Server (TCP 1433)" -Direction Inbound -Protocol TCP -LocalPort 1433 -Action Allow

# Optional: restrict to known IPs/networks (recommended for security)
# New-NetFirewallRule -DisplayName "SQL Server (TCP 1433) - Office" -Direction Inbound -Protocol TCP -LocalPort 1433 -RemoteAddress 203.0.113.10/32 -Action Allow

# SQL Server Browser (only if you use dynamic ports and need it)
New-NetFirewallRule -DisplayName "SQL Server Browser (UDP 1434)" -Direction Inbound -Protocol UDP -LocalPort 1434 -Action Allow

Connection and Quick Diagnostics

From a client/jump host (PowerShell):

# Default port example
Test-NetConnection YOUR_VPS_HOSTNAME_OR_IP -Port 1433

# Custom port example
Test-NetConnection YOUR_VPS_HOSTNAME_OR_IP -Port 51433

In SSMS, connect using:

Default instance + default port: HOSTNAME
Explicit port: HOSTNAME,1433
Named instance + explicit port (recommended): HOSTNAME\INSTANCE,51433

Basic SQL checks:

SELECT @@VERSION AS version;

EXEC sp_configure 'show advanced options', 1; 
RECONFIGURE;

EXEC sp_configure;  -- review current settings

Baseline performance settings (common starting points)

These settings depend on workload, but many production deployments set:

Max server memory (leave RAM for Windows + other services)
MAXDOP (often 4–8 as a starting point, then tune)
Cost Threshold for Parallelism (commonly raised above default 5 for OLTP workloads)

Example commands (adjust values to your VPS and workload):

EXEC sp_configure 'show advanced options', 1; 
RECONFIGURE;

-- Example: set MAXDOP to 8
EXEC sp_configure 'max degree of parallelism', 8; 
RECONFIGURE;

-- Example: raise cost threshold (common starting point)
EXEC sp_configure 'cost threshold for parallelism', 50; 
RECONFIGURE;

Post-Install Best Practices (Highly Recommended)

Patch management: keep Windows updated and apply SQL Server cumulative updates when appropriate.
Backups: configure full + differential + log backups (for Full recovery model) and test restores.
Defender exclusions: exclude SQL data/log/backup directories and sqlservr.exe where appropriate.
Monitoring: set PerfMon counters for disk latency, CPU, memory, and SQL-specific metrics.
Security: restrict firewall by IP, prefer VPN/jump host access, and avoid exposing SQL to the whole internet.

Common Installation Issues

Database Engine startup errors can be related to OS prerequisites or security settings. Ensure Windows is fully updated and that modern TLS settings are enabled.
Installer appears to freeze during long steps (image generation, feature setup): check setup logs and allow more time on smaller VPS plans, then re-try with updates applied.

Mini Checklist After Installation

Authentication mode chosen correctly; sa password is strong (if Mixed Mode is enabled).
TCP/IP enabled; static port configured and documented.
Firewall rules created; access restricted by IP/networks where possible.
TempDB reviewed (files, size, growth, location).
SQL Server Agent set to Automatic if you use jobs/maintenance.
Backups configured and restore test performed.

Deploy a Windows VPS for SQL Workloads

SQL Server needs stable disk latency and enough RAM. Choose a reliable Windows VPS or explore our VPS hosting plans to deploy MS SQL Server with predictable performance and clean network/security controls.