SQL Server 2022 installs on Windows Server 2025 in about fifteen minutes, and the installer gets you a working instance even if you click Next on every page. The defaults, though, are written for a laptop: memory unbounded, tempdb on the system drive, a collation you may not want, and no remote access. This guide walks through the installer page by page on a fresh Windows Server 2025 machine, says which setting matters on each page and why, and ends with the handful of post-install steps that turn an installed instance into one you can run a production database on. The same steps apply to a Windows VPS you administer yourself; on the managed SQL Server host MassiveGRID runs this installation for you and the licences come with the server.
Before you start: media, memory and disks
Three decisions are easier to make before the installer opens than after.
Which media
- Express is free and installs from a small web installer that downloads the rest. It is capped at 10 GB per database, 1,410 MB of buffer pool and the lesser of one socket or four cores, which is fine for a small application or a development copy. It is the edition most people run on a Windows VPS with SQL Server Express.
- Evaluation is the full Enterprise feature set for 180 days. Use it to test, then convert with a product key through Maintenance > Edition Upgrade in the Installation Center; no reinstall.
- Licensed media for Web, Standard or Enterprise comes with the product key embedded or asks for it on the Product Key page. On a hosted server with the licence included, the provider supplies the key; on MassiveGRID's SQL Server host the Web edition key is applied during provisioning.
Download the installer from Microsoft's SQL Server downloads page or the Evaluation Center, never from a third-party mirror. The ISO for the full editions is about 1.2 GB; the Express web installer is a few megabytes and then pulls roughly 300 MB.
Memory
Windows Server 2025 itself settles at around 2 GB of RAM after boot, and the SQL Server installer needs at least 1 GB free to run. In practice a 4 GB server is the floor for Express, 8 GB is a comfortable minimum for a Web or Standard instance that serves one application, and anything serious starts at 16 GB. You will cap SQL Server's memory on the Memory tab later; decide now how much the operating system keeps (2 GB on a small server, 4 GB from 16 GB up).
Disks
The installer puts data, log, tempdb and backups under the same directory on C: unless you tell it otherwise. On a VPS you may only have one volume, and that is acceptable for a small instance, but create the folders in advance so the Database Engine Configuration page can point at them:
New-Item -ItemType Directory -Path D:\SQLData, D:\SQLLog, D:\SQLTempDB, D:\SQLBackup -Force
If you add a second NVMe volume for SQL Server, format it with a 64 KB allocation unit size, which matches the 64 KB extents SQL Server reads and writes:
Format-Volume -DriveLetter D -FileSystem NTFS -AllocationUnitSize 65536 -NewFileSystemLabel "SQL" -Confirm:$false
Windows Server 2025 ships with .NET Framework 4.8 enabled, which SQL Server 2022 setup requires, so no feature has to be added first. Run Windows Update once before installing SQL Server, because the installer's Global Rules check will stop on a pending reboot.
Running the installer page by page
Mount the ISO (right-click, Mount) or run the Express installer and choose Custom, which opens the SQL Server Installation Center. Choose Installation > New SQL Server standalone installation. The pages below are the ones where a choice has consequences; the others can take their defaults.
Product Key and Edition
Choose Evaluation, Express or Developer under the free editions, or enter the product key. The edition you pick here decides the limits the instance runs under; you can move up later with Edition Upgrade but not down.
Microsoft Update
Tick Use Microsoft Update to check for updates. SQL Server cumulative updates then arrive through Windows Update, which is how a self-managed server stays patched without someone remembering to do it. Untick it only if you patch SQL Server on a change window of your own.
Feature Selection
Install the Database Engine Services and nothing else unless you know you need it. Every extra feature is a service with memory of its own and an attack surface to patch:
- SQL Server Replication, only if you will publish or subscribe.
- Full-Text and Semantic Extractions, needed by some CMSs and by applications that use CONTAINS() queries. Cheap to add now, awkward to add later.
- Machine Learning Services, PolyBase, Analysis Services, Integration Services, Reporting Services: leave them off. Reporting Services and SSMS are separate downloads in 2022 anyway.
Set the instance root directory to the data drive if you have one; the shared feature directories can stay on C:.
Instance Configuration
The default instance (MSSQLSERVER) listens on TCP 1433 and is addressed by the server name alone. A named instance (for example SERVER\SQL2022) gets a dynamic port and needs the SQL Browser service or an explicit port in every connection string. Pick the default instance unless this machine will host several versions side by side. Express installs as a named instance called SQLEXPRESS by default; change it to a default instance here if you prefer plain connection strings.
Server Configuration: service accounts and collation
Leave the virtual service accounts (NT Service\MSSQLSERVER) unless the instance must reach a file share with a domain account. Tick Grant Perform Volume Maintenance Task privilege: that is instant file initialisation, which lets data files grow without zeroing every page first and turns a minutes-long restore into seconds. Set SQL Server Agent to Automatic; it is manual by default on some editions and you will want it for backup jobs. Express has no Agent at all.
On the Collation tab the default follows the Windows locale, usually SQL_Latin1_General_CP1_CI_AS on an English server. Change it only if the application documentation says so: a collation mismatch between a database and tempdb produces errors that are painful to fix later. Applications written for case-sensitive or UTF-8 collations (Latin1_General_100_CI_AS_SC_UTF8, for example) will say so in their requirements.
Database Engine Configuration
This page has five tabs and is where most of the value is.
- Server Configuration: choose Windows authentication mode if every client is a Windows account on this server or domain, or Mixed Mode if an application connects with a SQL login (most web applications do). Mixed Mode enables the sa account, so give it a long random password and plan to disable it after creating your own sysadmin login. Click Add Current User so your administrator account is a sysadmin; the installer no longer adds local administrators automatically.
- Data Directories: point user database, log, and backup directories at the folders you created. Keeping logs on a separate volume matters more on spinning disks than on NVMe, but separate folders keep backups and growth visible.
- TempDB: the installer proposes one data file per core up to eight, which is the right rule. Set the initial size of each file to something realistic for the server (1 GB on a small instance, more if the application is known to use tempdb heavily), autogrowth to a fixed 256 MB or 512 MB rather than a percentage, and put the files on the fastest volume.
- MaxDOP (2019 and later): the installer suggests a value from the core count. On a 2 or 4 vCPU server the suggestion will be 2 or 4; accept it.
- Memory: choose Recommended, which caps max server memory so the operating system keeps a share. Check the figure against the rule in the next section and type a lower number if the server also runs IIS or anything else.
Click through Ready to Install, and the install takes five to ten minutes on NVMe. Restart if the completion page asks for it.
After the installer finishes: five steps
1. Install SQL Server Management Studio
SSMS is a separate download from Microsoft Learn and installs in a few minutes. On a server you will administer over RDP it is the easiest tool; on a server you want to keep lean, install SSMS on your workstation instead and connect remotely once the firewall is open. Microsoft announced the retirement of Azure Data Studio with support ending in February 2026 and points to SSMS 21 and the VS Code extensions instead, so SSMS is the tool to install, as read on 3 November 2026.
2. Verify the instance
Open SSMS, connect to localhost (or localhost\SQLEXPRESS for a named Express instance) and run:
SELECT @@VERSION;
SELECT SERVERPROPERTY('Edition') AS Edition,
SERVERPROPERTY('ProductLevel') AS Level,
SERVERPROPERTY('ProductUpdateLevel') AS CU;
The first line of @@VERSION names the version and build; the second query tells you the edition and which cumulative update you are on. If the CU column is NULL you are on RTM and Windows Update will offer the latest CU shortly.
3. Confirm memory, tempdb and instant file initialisation
SELECT name, value_in_use FROM sys.configurations
WHERE name IN ('max server memory (MB)', 'max degree of parallelism', 'cost threshold for parallelism');
SELECT name, size * 8 / 1024 AS size_mb, growth FROM tempdb.sys.database_files;
SELECT instant_file_initialization_enabled FROM sys.dm_server_services
WHERE servicename LIKE 'SQL Server (%';
If max server memory shows 2147483647, the installer's Memory tab was skipped and the instance will take every byte Windows has. Set it now; the sizing post on memory, tempdb and disk settings on a VPS has the table for 4 to 32 GB servers:
EXEC sp_configure 'show advanced options', 1; RECONFIGURE;
EXEC sp_configure 'max server memory (MB)', 5120; RECONFIGURE;
4. Enable TCP/IP and open the firewall, if anyone connects remotely
Out of the box the Database Engine accepts Shared Memory connections from the same machine and nothing else. Open SQL Server Configuration Manager, go to SQL Server Network Configuration > Protocols for MSSQLSERVER, enable TCP/IP, set the port under IP Addresses > IPAll > TCP Port to 1433 and restart the service. Then add a firewall rule restricted to the addresses that need it:
New-NetFirewallRule -DisplayName "SQL Server 1433" -Direction Inbound -Protocol TCP -LocalPort 1433 -RemoteAddress 203.0.113.10 -Action Allow
Never open 1433 to any address. The full set of options, including SQL Browser for named instances and the connection errors you will meet, is in the remote connections guide.
5. Take a first backup and schedule the rest
Before any data goes in, back up master and msdb once so you have a baseline, then set up the maintenance jobs in SQL Server Agent (or Task Scheduler on Express, which has no Agent). The backups guide covers recovery models, maintenance plans and backup to URL.
BACKUP DATABASE master TO DISK = 'D:\SQLBackup\master.bak' WITH COMPRESSION, CHECKSUM;
BACKUP DATABASE msdb TO DISK = 'D:\SQLBackup\msdb.bak' WITH COMPRESSION, CHECKSUM;
Installing without the wizard
Once you know the answers, the whole thing is one command, which is how you rebuild a staging server identically or script a fleet. Save a ConfigurationFile.ini from the Ready to Install page of a wizard run (the path is shown at the bottom), then:
.\setup.exe /ConfigurationFile=ConfigurationFile.ini /IAcceptSQLServerLicenseTerms /SAPWD="a-long-random-password" /Q
Or pass everything on the command line for a default instance with Mixed Mode, your account as sysadmin, four tempdb files and a memory cap:
.\setup.exe /Q /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=MSSQLSERVER ^
/SQLSVCACCOUNT="NT Service\MSSQLSERVER" /SQLSVCINSTANTFILEINIT=True ^
/SQLSYSADMINACCOUNTS="SERVER\Administrator" /SECURITYMODE=SQL /SAPWD="a-long-random-password" ^
/SQLTEMPDBFILECOUNT=4 /SQLTEMPDBFILESIZE=1024 /SQLTEMPDBFILEGROWTH=256 ^
/SQLMAXMEMORY=5120 /SQLMAXDOP=2 /TCPENABLED=1 ^
/SQLUSERDBDIR="D:\SQLData" /SQLUSERDBLOGDIR="D:\SQLLog" /SQLTEMPDBDIR="D:\SQLTempDB" /SQLBACKUPDIR="D:\SQLBackup" ^
/IACCEPTSQLSERVERLICENSETERMS /UPDATEENABLED=True
The parameter names are documented on Microsoft Learn under "Install SQL Server from the command prompt"; the ones above were checked against that page on 3 November 2026.
When not to do any of this
Installing SQL Server is the easy part; keeping it patched, backed up, monitored and recoverable is the part that costs time every month. If the database is the product, or the person who would run it is also the developer, the managed route is usually cheaper than the hours. On MassiveGRID's SQL Server hosting the Managed Cloud Dedicated Server arrives with Windows Server Standard and SQL Server Web installed and licensed per vCore under Microsoft's SPLA, from $86.34 a month for 2 reserved vCores, 8 GB and 128 GB of NVMe; MassiveGRID patches and hardens the operating system, takes daily backups and monitors it around the clock, and the Proxmox HA cluster restarts the VM on another node if the hardware fails. You still own the instance, the logins and the databases, so everything in the sections above about memory, tempdb and backups still applies to you, just without the installer. Web edition is restricted by Microsoft's Services Provider Use Rights to public, internet-facing applications; for an internal line-of-business system, see SQL Server Standard hosting.
If you prefer to run the installer yourself, a Windows VPS from $3.99 a month starts on Microsoft's 180-day Windows Server evaluation; a 2 vCPU, 8 GB, 64 GB server on reserved cores for a Standard edition database you license yourself is $26.20 a month on the Windows Dedicated VPS before the Windows licence at $6.31 per vCPU.
Frequently Asked Questions
Does SQL Server 2022 support Windows Server 2025?
Yes. Microsoft lists Windows Server 2025 as a supported operating system for SQL Server 2022 and the installer runs without compatibility warnings, as read on Microsoft Learn on 3 November 2026. SQL Server 2019 is also supported on Windows Server 2025; SQL Server 2017 and earlier are not.
Should I choose Windows authentication or Mixed Mode?
Windows authentication if every connecting user and service runs as a Windows account on the same server or domain. Mixed Mode if an application connects with a SQL login, which most web applications do. With Mixed Mode, set a long random password for sa, create your own sysadmin login, and then disable sa.
How much RAM does SQL Server 2022 need?
Microsoft states a 1 GB minimum for the Database Engine, but that is for the installer, not for running a database. Windows Server 2025 uses about 2 GB on its own, so 4 GB is the practical floor for SQL Server Express, 8 GB for a single-application Web or Standard instance, and 16 GB or more for anything busy. Whatever the size, cap max server memory so the operating system keeps 2 to 4 GB.
Can I upgrade SQL Server Express or Evaluation to Standard without reinstalling?
Yes. Open the SQL Server Installation Center, choose Maintenance, then Edition Upgrade, and enter the product key for the edition you have licensed. The instance restarts and the new limits apply; the databases are untouched. The upgrade goes upward only (Express to Web or Standard, Evaluation to any paid edition); moving down means a reinstall.
Is SQL Server 2022 still the version to install in late 2026?
For production, yes. SQL Server 2022 is in mainstream support until January 2028 and extended support until January 2033, and it is the version most third-party applications certify. SQL Server 2025 reached general availability in November 2025; check that your application vendor supports it before choosing it for a new server. Verify the dates on Microsoft's lifecycle pages, which were read on 3 November 2026.
A SQL Server host that arrives installed, licensed and patched
MassiveGRID SQL Server hosting is a Managed Cloud Dedicated Server with Windows Server Standard and SQL Server Web licensed per vCore and installed for you, from $86.34 a month for 2 reserved vCores, 8 GB and 128 GB NVMe. Daily backups, OS patching and 24/7 monitoring included, HA failover on a Proxmox cluster, New York, London, Frankfurt or Singapore.
See SQL Server hostingFurther Reading
- Microsoft Learn: SQL Server 2022 hardware and software requirements
- Microsoft Learn: Install SQL Server from the Installation Wizard
- Microsoft Learn: Install SQL Server from the command prompt
- Microsoft Learn: Database instant file initialization
- Microsoft Learn: Download SQL Server Management Studio