SQL Server 2022 installs in about fifteen minutes — but five screens in that setup decide things you will live with for years. Edition, collation, service accounts, file locations and memory: set them right now, or pay for them later.
Most SQL Server installs do not fail during setup. They fail slowly, months later — when the database outgrows a 10 GB Express limit nobody knew about, when backups were never set up, or when the server grabs every gigabyte of RAM and starves Windows itself. This guide walks the full install in order and stops at each screen that actually matters. The panel below shows the choices we are about to make, before we make them.
Download SQL Server 2022 only from Microsoft's website. The small web installer offers three free editions and downloads the full media if you choose the Custom option — take the full download so you can reinstall or repair later without going back to the internet. Installing from random download sites is how people end up with pre-activated, outdated or bundled installers; there is no reason to risk it on a database server.
The honest edition picture is simple. Developer edition is completely free and contains every Enterprise feature — but its licence is for development and testing only, never for a live production database. Express edition is free even for production, but each database is capped at 10 GB, the engine can use only about 1.4 GB of RAM for its buffer pool, and there is no SQL Server Agent for scheduled jobs. Standard and Enterprise are paid licences for real production work. If you are learning or building an application, pick Developer. We have a full edition-by-edition comparison in a separate guide.
Start setup, choose a new installation, and pass the setup support rules. A pending restart from Windows Update is the most common blocker — restart the machine first and the rule goes green. On the Feature Selection screen, the one feature almost everyone needs is Database Engine Services. Skip Analysis Services, Reporting Services and Integration Services unless you know you will use them; every extra service is another process running forever and another thing to patch. You can add features later from the same setup.
Setup now asks for an instance. The default instance is reached by the plain computer name and listens on port 1433; a named instance adds a backslash name like SERVER\SQLEXPRESS and normally uses a dynamic port. One machine can host several named instances, which is genuinely useful for testing two versions side by side. For your first and main install, take the default instance — every tool and tutorial assumes it, and connection strings stay short.
On the Server Configuration page, setup shows the account each service will run as. The default virtual accounts (for example NT SERVICE\MSSQLSERVER) are the safe choice for a single machine: each service gets its own identity with only the rights it needs. In a company domain, use a separate low-privilege domain account or a group Managed Service Account per service. What you should never do is run the database engine as Local System or as a domain administrator — if the service is ever abused, it inherits everything that account can do. Leave the startup types as setup suggests: engine Automatic, Agent Manual until you start scheduling jobs.
The same page has a Collation tab. Collation decides how text is sorted and compared — whether A equals a, and how accents are treated. The installer default for English systems, SQL_Latin1_General_CP1_CI_AS, is case-insensitive and accent-sensitive, and it suits most applications. Here is the honest warning: the server collation is chosen at install and changing it later means rebuilding the system databases — an expert job with downtime. Individual databases can override it later, so do not overthink; but if an application vendor specifies a collation, set it now while it costs nothing.
On the Database Engine Configuration page, pick Mixed Mode unless you are certain every user and application will use Windows logins. Mixed Mode enables the built-in sa account — set a genuinely strong password for it and store it in your password manager, because sa is the first account attackers try. Also add the current Windows user (and your admin group) as SQL Server administrators on this screen; forgetting this is why many first installs end with the owner locked out of their own server. Windows Authentication remains the safer everyday login; Mixed Mode is there for the applications that need a SQL login.
Stay on that page and open the Data Directories and TempDB tabs. Setup will happily put everything inside C:\Program Files — acceptable on a learning laptop, poor on a real server. Data files and transaction logs work the disk differently, so on a machine with more than one drive, put data on one volume and logs on another; put backups somewhere else again, ideally off the machine entirely. On a single SSD the split matters less, but still move the folders to a clean path like D:\SQLData so the system drive stays free. For TempDB, setup suggests multiple data files matched to your CPU cores (up to eight) — accept that suggestion; it removes a well-known bottleneck.
SQL Server is designed to use memory aggressively: by default its max server memory is effectively unlimited, so over days it will cache data until it holds nearly all the RAM on the machine. That is correct behaviour for a dedicated database server and a nasty surprise on a shared one — Windows and every other app get squeezed. The 2022 setup includes a Memory tab: accept its recommended cap, or set your own leaving at least a few gigabytes for the operating system. You can change it later without a reinstall, as this example for a 16 GB machine shows:
EXEC sp_configure 'max server memory (MB)', 10240; followed by RECONFIGURE;When setup completes with a green summary, install SQL Server Management Studio (SSMS) — it is a separate free download and is not part of the server setup. Connect to the server name, run SELECT @@VERSION; and create a throwaway test database, add a table and delete it again. That two-minute exercise proves the engine, your login and basic permissions end to end. If the first connection instead throws a certificate or encryption error, do not keep clicking — that exact error has its own causes and we cover it in a separate fix guide.
SELECT @@VERSION; should report Microsoft SQL Server 2022Watch the complete SQL Server 2022 installation in the video — every setup screen, the exact clicks, and the first connection in SSMS, step by step.
▶️ Watch Full VideoIt is free to download and use, and it includes every Enterprise feature — but the licence allows development and testing only. The moment a database serves a real business or real users in production, you need a paid Standard or Enterprise licence, or the genuinely free Express edition within its limits. Developer on a production server is the most common SQL licensing mistake in small offices.
The Database Engine installs on Windows 10 and Windows 11 as well as Windows Server, which is why Developer and Express are so popular on workstations and laptops. For a production server that others depend on, run it on Windows Server on a machine that stays on — but for learning and development, your normal Windows PC is perfectly fine.
No — SSMS has been a separate download for years and is not installed by the server setup. Download SQL Server Management Studio free from Microsoft, install it on the same machine (or on your own PC and connect remotely), and log in with the Windows account you added as administrator during setup.