Install SQL Server 2025 on Windows Server VPS: Requirements & Setup

In short

To install SQL Server 2025 on a Windows Server VPS, first confirm the server meets Microsoft's current requirements: a supported x64 Windows version, at least a 1.4 GHz processor, at least 1 GB RAM for non-Express editions, at least 6 GB of available disk space for SQL Server itself, and .NET Framework 4.7.2. For a new deployment, Windows Server 2025 or Windows Server 2022 are both supported choices.

Then choose the correct SQL Server edition, use the full Custom setup wizard, configure authentication and data paths, tune TempDB and max server memory, patch the instance to your current Microsoft servicing baseline, and open TCP 1433 only to trusted IPs or private networks.

Raff Windows VMs can provide the Windows Server layer for this self-managed SQL Server setup. SQL Server production licensing is separate from the Windows Server licence included with a Raff Windows VM.

SQL Server 2025 requirements

Microsoft's current SQL Server 2025 hardware and software requirements are installation minimums, not production sizing targets.

SQL Server 2025 is supported on Windows Server 2025, Windows Server 2022, and Windows Server 2019. It is not supported on Windows Server 2016. Microsoft also supports SQL Server 2025 on supported Windows 10 and Windows 11 editions, but this guide focuses on Windows Server.

Server Core is also supported on supported Windows Server releases.

Minimum requirements are not production sizing

A server meeting Microsoft's minimum requirements can install SQL Server 2025, but that does not mean it is sized for a real database workload.

For current Raff pricing context, a 4 vCPU / 8 GB / 120 GB Windows VM is $55.99/month total, made up of $40.99 compute plus the $15 Windows Server Standard SPLA licence. An 8 vCPU / 16 GB / 180 GB Windows VM is $91.99/month total. SQL Server Standard or Enterprise licensing, backup storage, application licensing, and other optional services are separate.

For broader planning, use Windows Server Sizing by Workload.

Which SQL Server edition should you install?

SQL Server 2025 added separate Standard Developer and Enterprise Developer editions. Developer editions are for development and testing, not production.

This guide uses Standard Developer because it is suitable for development, staging, and installation validation. The setup flow for paid Standard is similar; the production licensing path is different.

Do not run Developer or Evaluation editions as long-term production licensing.

What you will build

This guide installs a clean SQL Server 2025 instance on a Windows Server VPS.

Windows Server VPS
  ↓
SQL Server 2025
  ├── Database Engine
  ├── SQL Server Agent where supported/needed
  ├── TempDB
  ├── Data files
  ├── Log files
  ├── Backups
  └── Firewall / private access

For a small workload, the app and SQL Server can run on one VM. As the workload grows, separating the application and database onto different VMs over a private network can improve isolation and troubleshooting.

What you'll need

Before starting, prepare:

• a Raff Windows VM or another supported Windows Server environment;
• Windows Server 2022 or Windows Server 2025;
• local Administrator access;
• no pending Windows reboot;
• SQL Server 2025 installation media;
• SQL Server Management Studio on your workstation or server;
• a password manager for the sa password if you choose Mixed Mode;
• a backup plan before production data is added.

Quick context: what changed in SQL Server 2025

Practical SQL Server 2025 changes include:

• SQL Server 2025 is version 17.x.
• General availability was build 17.0.1000.7 on November 18, 2025.
• Standard edition supports up to 32 cores and a 256 GB buffer pool.
• Express supports up to 50 GB per relational database.
• Web edition is discontinued.
• Express with Advanced Services is discontinued because base Express now includes those capabilities.
• Standard Developer and Enterprise Developer are separate developer editions.
• Resource Governor is available in Standard and Standard Developer.
• SQL Server 2025 includes new vector and AI-related database features, but preview features should not be treated as production-ready until Microsoft marks them accordingly.

As of September 17, 2026, Microsoft lists CU8, build 17.0.4075.5, as the latest cumulative update and also lists a September 2026 security-servicing build on the CU8 branch. Before production use, check Microsoft's current SQL Server 2025 build page and patch according to your chosen CU/GDR servicing policy rather than relying only on the RTM build in an old screenshot.

Step 1 — Prepare the Windows Server VPS

Connect to the Windows Server VPS over RDP as Administrator.

Before running setup:

1. Install pending Windows updates.
2. Reboot the server.
3. Confirm you can reconnect over RDP.
4. Confirm the system drive has enough free space.
5. Create a clean SQL folder structure.

Run PowerShell as Administrator:

New-Item -ItemType Directory -Path "C:\SQL\Data" -Force
New-Item -ItemType Directory -Path "C:\SQL\Logs" -Force
New-Item -ItemType Directory -Path "C:\SQL\Backups" -Force
New-Item -ItemType Directory -Path "C:\SQL\TempDB" -Force

This keeps user databases, transaction logs, backups, and TempDB easier to manage than leaving everything under C:\Program Files\Microsoft SQL Server\.

If you later use separate disks or volumes, keep the same idea with dedicated paths such as D:\SQL\Data, L:\SQL\Logs, and T:\SQL\TempDB.

Step 2 — Get SQL Server 2025 media onto the server

Windows Server 2025 supports WinGet through the App Installer system component, but availability can depend on the server's update state. If winget is present, you can use it to locate packages. For predictable production setup, Microsoft's official SQL Server download and licensing channels remain the source of record for installation media.

Option 1: Use WinGet when it is available

Check first:

winget --version

Then search rather than assuming a package ID:

winget search "SQL Server 2025"

If you use a WinGet package to obtain media, still use the full setup wizard for a production-style install so you can control features, authentication, data paths, TempDB, memory, and service configuration.

Option 2: Download media from Microsoft

Download SQL Server 2025 from Microsoft's SQL Server download or licensing channel appropriate to the edition.

For Standard or Enterprise production media, use the entitlement provided through your Microsoft licensing route. For free developer or Express editions, use Microsoft's current SQL Server download resources.

Use the full setup wizard instead of a one-click Basic install when you need deliberate control over:

• edition;
• feature selection;
• authentication;
• service startup;
• data directories;
• TempDB;
• MaxDOP;
• memory;
• firewall planning.

Option 3: Use Evaluation only for a temporary test

Microsoft provides a 180-day SQL Server Evaluation edition for temporary Enterprise-feature testing, proof-of-concept work, and migration validation. Do not use Evaluation as a permanent production licensing plan.

Do not run SQL Server setup from an ISO mounted through a local RDP redirected drive. Put the media on the server itself or on a network share the server can reliably reach.

Step 3 — Run the install wizard

From PowerShell on the Windows Server VPS, launch setup as Administrator:

Start-Process -FilePath "C:\SQL2025\StdDev_ENU\setup.exe" -Verb RunAs

Select:

Installation
  → New SQL Server standalone installation or add features to an existing installation

Edition

For this guide:

Specify a free edition
  → Standard Developer

For production, use the paid Standard or Enterprise licensing path appropriate to your Microsoft entitlement.

License terms, setup rules, Microsoft Update, and product updates

Accept the applicable licence terms. If Microsoft Update is offered, enable it if that matches your patching policy.

If setup reports a pending restart, cancel setup, reboot, reconnect, and run setup again.

Install Rules: the Windows Firewall warning is expected

Do not disable Windows Firewall just to clear the warning.

Use this model:

Install SQL Server.
Decide who needs remote access.
Open only the required port.
Restrict by source IP or private network.

Azure Extension for SQL Server: skip unless you need Azure Arc

Leave Azure Extension unchecked unless the deployment specifically requires Azure Arc or Azure-connected SQL features. You can register later if a real requirement appears.

Feature Selection: install only what the workload needs

The original Raff lab selected Database Engine Services, Replication, and Full-Text Search. For a fresh production deployment, do not treat all three as a universal minimum.

Start with:

• Database Engine Services: required for the database engine.

Add only when the application needs them:

• SQL Server Replication: only for a real replication design.
• Full-Text Search: when the application uses full-text capabilities.
• PolyBase, Analysis Services, Integration Services, language extensions, or AI-related components: only when the workload requires them.

A smaller installation surface is easier to patch, secure, and troubleshoot.

Instance Configuration: default instance for a simple single-instance VM

For a single-purpose SQL VM, a default MSSQLSERVER instance is often simpler. Use a named instance when multiple instances, side-by-side versions, or a vendor requirement justify it.

Server Configuration: Agent and instant file initialization

For Standard, Enterprise, or Developer editions where SQL Server Agent is part of the deployment, set Agent to Automatic if you will use scheduled jobs, alerts, or backup tasks.

Grant Perform Volume Maintenance Tasks to the SQL Server Database Engine service when instant file initialization fits your security policy and workload.

Leave SQL Server Browser disabled for a default instance unless the architecture requires it. Keep the default collation unless the application vendor requires a specific collation.

Database Engine Configuration: authentication

For a standalone, non-domain-joined Windows VPS, Mixed Mode can be practical when applications require SQL logins.

If you use Mixed Mode:

• set a long, unique sa password;
• store it in a password manager;
• add an attributable Windows administrator as SQL Server admin;
• create dedicated application logins later;
• do not use sa as the normal application login.

For domain-joined environments, Windows Authentication may be preferable where the application supports it.

Data Directories

Use the folder structure created earlier:

On a single-volume VPS, separate folders do not create separate physical I/O paths. They provide operational clarity. Use genuinely separate volumes only when the workload and recovery design justify them.

TempDB

The original Raff lab used four equal TempDB data files on a 4 vCPU VM. Treat that as a tested starting configuration, not a universal rule.

For small and mid-sized SQL Server VMs, keep TempDB files equal-sized and use fixed MB growth. Start with the setup wizard's recommendation and adjust from measured contention, TempDB growth, and workload behavior.

For deeper tuning, use Configure TempDB for MSSQL Performance.

MaxDOP

Use the installer recommendation as the starting point, then tune from the workload. Avoid copying a MaxDOP value from another server without considering CPU topology, query concurrency, and application behavior.

Memory and FILESTREAM

Leave FILESTREAM disabled unless the application requires it.

After installation, set max server memory (MB) so Windows and non-SQL processes retain enough RAM. The dedicated SQL Server Max Server Memory guide owns the detailed sizing guidance.

Ready to Install

Before clicking Install, review edition, selected features, instance name, service startup, data paths, TempDB, MaxDOP, SQL admins, and authentication mode.

SQL Setup also writes a configuration file. Do not publish that file if it includes sensitive paths, usernames, or product-key-related information.

Click Install and review the setup summary before moving on. If any selected feature fails, inspect the SQL Setup logs and resolve the root cause rather than accepting a partial installation.

Step 4 — Cap SQL Server memory

SQL Server uses available memory aggressively by design. A Windows Server VPS also needs RAM for Windows, security software, backups, monitoring, RDP administration, and any co-hosted applications.

Example for an 8 GB VM:

EXEC sys.sp_configure 'show advanced options', 1;
RECONFIGURE;
EXEC sys.sp_configure 'max server memory (MB)', 6144;
RECONFIGURE;

EXEC sys.sp_configure 'max server memory (MB)';

Treat 6144 as an example for a mostly dedicated SQL Server, not a universal 8 GB value. Shared SQL + IIS/RDP workloads usually need a larger Windows/non-SQL reserve.

For current guidance and pressure checks, use SQL Server Max Server Memory.

Step 5 — Patch SQL Server 2025 to your current servicing baseline

Do not leave a production instance on the RTM build simply because the installation succeeded.

As of September 17, 2026, Microsoft's SQL Server 2025 build page lists CU8 (17.0.4075.5) as the latest cumulative update and a September 2026 security build on the CU8 branch. Microsoft servicing can change after this article is updated, so use the current build-history page before patching.

Verify after servicing:

SELECT @@VERSION;

and:

SELECT SERVERPROPERTY('ProductVersion') AS ProductVersion,
       SERVERPROPERTY('ProductLevel') AS ProductLevel,
       SERVERPROPERTY('ProductUpdateLevel') AS ProductUpdateLevel,
       SERVERPROPERTY('Edition') AS Edition;

Record the build and patch date in the server change log.

Step 6 — Install SQL Server Management Studio

SQL Server Management Studio is maintained separately from the SQL Server engine.

A practical approach is:

• install SSMS on an administrator workstation when remote management is preferred;
• install it on the server only when local GUI administration is useful;
• keep SSMS updated independently from SQL Server servicing.

Use localhost for local management or the approved private/trusted address for remote administration.

Step 7 — Enable TCP/IP only when remote SQL access is required

If applications connect only from the same VM, you may not need remote SQL exposure.

If another application server or trusted admin workstation needs SQL access, enable TCP/IP deliberately in SQL Server Configuration Manager and use a documented static port, commonly TCP 1433 for a default instance.

Restart the SQL Server service after changing protocol settings.

Step 8 — Restrict Windows Firewall to trusted SQL clients

Do not expose TCP 1433 to the whole internet.

Example allowing one trusted documentation IP:

New-NetFirewallRule `
  -DisplayName "SQL Server 2025 TCP 1433 - Trusted Source" `
  -Direction Inbound `
  -Protocol TCP `
  -LocalPort 1433 `
  -RemoteAddress "203.0.113.10" `
  -Action Allow

Replace the documentation address with the real office, VPN, or private-network source.

Prefer, in order where practical:

• same-server connections;
• private networking between app and database VMs;
• VPN or controlled management path;
• narrow source-IP allowlisting;
• no public SQL port when it is not required.

Step 9 — Create a test database

CREATE DATABASE RaffSqlTest;
GO

USE RaffSqlTest;
GO

CREATE TABLE dbo.HealthCheck
(
    Id int IDENTITY(1,1) PRIMARY KEY,
    CreatedAt datetime2 NOT NULL DEFAULT sysdatetime(),
    Message nvarchar(200) NOT NULL
);
GO

INSERT INTO dbo.HealthCheck (Message)
VALUES (N'SQL Server 2025 is working.');
GO

SELECT * FROM dbo.HealthCheck;
GO

Verify file placement:

SELECT name, physical_name
FROM sys.master_files
WHERE database_id = DB_ID('RaffSqlTest');

Step 10 — Create a dedicated application login

Do not give an application the sa credential.

CREATE LOGIN app_user WITH PASSWORD = 'Use-A-Strong-Unique-Password-Here!';
GO

USE RaffSqlTest;
GO

CREATE USER app_user FOR LOGIN app_user;
GO

ALTER ROLE db_datareader ADD MEMBER app_user;
ALTER ROLE db_datawriter ADD MEMBER app_user;
GO

For production, grant only the permissions the application actually requires.

Step 11 — Create and verify the first backup

BACKUP DATABASE RaffSqlTest
TO DISK = 'C:\SQL\Backups\RaffSqlTest_full.bak'
WITH INIT, COMPRESSION, CHECKSUM, STATS = 10;
GO

Verify it:

RESTORE VERIFYONLY
FROM DISK = 'C:\SQL\Backups\RaffSqlTest_full.bak'
WITH CHECKSUM;
GO

A complete production backup plan also needs retention, off-server copies, alerting, and actual restore testing. See SQL Server Backup Strategy.

Step 12 — Verify the final install

Check services:

Get-Service -Name MSSQLSERVER, SQLSERVERAGENT |
  Format-Table Name, Status, StartType

Check the SQL build and edition:

SELECT @@VERSION AS Version,
       SERVERPROPERTY('Edition') AS Edition,
       SERVERPROPERTY('ProductLevel') AS ProductLevel,
       SERVERPROPERTY('ProductUpdateLevel') AS ProductUpdateLevel;

A final production verification should confirm:

• the SQL Server service is running;
• Agent is running when the chosen edition and automation design use it;
• the edition matches the intended licence;
• the SQL build matches the current servicing baseline;
• data, log, TempDB, and backup paths match the design;
• max server memory and MaxDOP are deliberate values;
• remote SQL access is restricted to intended sources;
• backups and restore testing are configured.

Common mistakes

Pending Windows restart blocks setup

Reboot before SQL Server setup if Windows reports a pending restart.

Treating a Basic install as production design

Use Custom setup when production requirements include deliberate feature selection, authentication, data paths, TempDB, service configuration, and firewall controls.

Installing features "just in case"

Replication, Full-Text, PolyBase, Analysis Services, Integration Services, and language extensions should be installed because the workload needs them, not because they appear in a generic checklist.

Leaving TempDB unreviewed

Start with sensible equal-sized files and fixed MB growth, then tune from measured TempDB behavior.

Leaving max server memory effectively unlimited on a shared VM

Reserve memory for Windows and every non-SQL workload.

Using sa as the application login

Create a dedicated login with only the permissions the application needs.

Installing SQL Server on a domain controller

Use a dedicated Windows Server VM for SQL Server whenever practical.

Opening TCP 1433 to the internet

Use private networking, VPN, or narrow allowlists. Do not expose the database listener broadly.

Forgetting SQL Server servicing

The RTM build is not the current production patch level. Check Microsoft's SQL Server 2025 build history before go-live and during maintenance cycles.

When to use Standard, Enterprise, Express, or Developer

Use Standard Developer or Enterprise Developer only for development and test scenarios.

Use Express when the workload fits its CPU, memory, feature, and 50 GB database limits.

Use Standard for many production business applications, ERP databases, internal tools, IIS/ASP.NET application databases, and moderate reporting workloads.

Use Enterprise when the workload requires Enterprise-only scale, availability, or feature capabilities.

SQL Server Standard and Enterprise production licensing is separate from the Windows Server SPLA licence included with a Raff Windows VM. Confirm SQL Server licence rights through the customer's Microsoft licensing agreement, licensing partner, or other valid entitlement before production deployment.

Recommended setup by workload

How Raff fits SQL Server hosting

Raff provides the Windows Server VM layer for self-managed SQL Server deployments. A common small production pattern is to keep the application and database separate once the workload justifies it:

App VM
  ↓
Private network
  ↓
SQL Server VM
  ↓
Backups / monitoring

Use Raff SQL Server Hosting for the commercial overview, Raff Windows VM for the underlying Windows compute options, and pricing for the current VM ladder.

Raff supports 3,000+ customers and 15,000+ VMs, with a 99.9% SLA. SQL Server configuration, database security, application compatibility, SQL Server production licensing, backups, and restore design remain workload-specific responsibilities unless a separate managed service explicitly covers them.

Tested on Raff

Tested on Raff: SQL Server 2025 Standard Developer Edition installed on a Raff Windows Server 2025 VM, 4 vCPU / 8 GB RAM / 120 GB NVMe, Windows Server 2025 Standard build 26100, us-east region, on April 24, 2026. Engineer: Serdar Tekin.

The original test verified media acquisition, Custom setup, Azure Extension disabled, Mixed Mode authentication, four 512 MB TempDB files at C:\SQL\TempDB, MaxDOP 4, C:\SQL\Data / C:\SQL\Logs / C:\SQL\Backups, SQL Server Agent set to Automatic, Perform Volume Maintenance Tasks granted, a restricted TCP 1433 firewall rule, local/remote connectivity, and SELECT @@VERSION. The screenshots above are from that test. September 2026 source revalidation does not claim a new benchmark.

What's next

• Connect to a Windows VPS via RDP
• Windows Server Sizing by Workload
• SQL Server Max Server Memory
• SQL Server Backup Strategy
• Windows Server 2022 vs 2025 vs 2019
• Raff SQL Server Hosting
• Raff Windows VM

Sources

• Microsoft Learn: SQL Server 2025 hardware and software requirements
• Microsoft Learn: SQL Server and Windows compatibility matrix
• Microsoft Learn: SQL Server 2025 release notes
• Microsoft Learn: Editions and supported features of SQL Server 2025
• Microsoft Learn: SQL Server 2025 build versions
• Microsoft Learn: Install SQL Server
• Microsoft Learn: Configure Windows Firewall for SQL Server access
• Microsoft Learn: tempdb database
• Microsoft Learn: Server memory configuration options
• Microsoft Learn: Configure MaxDOP
• Microsoft Learn: Install SQL Server Management Studio
• Microsoft Learn: WinGet
• Sources revalidated: 2026-09-17

Microsoft, Windows Server, SQL Server, and SQL Server Management Studio are trademarks of Microsoft Corporation. Raff is an independent infrastructure provider and is not affiliated with, sponsored by, or endorsed by Microsoft Corporation.