Install SQL Server 2022

Pick the Edition and Download from Microsoft

Download SQL Server 2022 only from Microsoft's official website. The small web installer offers the free editions and, with the Custom option, downloads the full media — take the full download so you can reinstall or repair later without going back to the internet. Never install a database server from random download sites: pre-activated, outdated or bundled installers are a real risk.

The edition picture is simple. Developer is completely free and contains every Enterprise feature, but its licence is for development and testing only. Express 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 the paid editions for real production work. Learning or building an application? Pick Developer.

Start Setup and Select Only the Features You Need

Run setup as administrator and choose New SQL Server stand-alone installation, then 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, tick Database Engine Services — the one feature almost everyone needs. 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, and features can be added later from the same setup. Leave the instance root directory on the system drive under C:\Program Files — the data files will go elsewhere in a later step.

Name the Instance — Default Is Usually Right

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 and normally uses a dynamic port — in SSMS you connect to it like this:

SERVER\SQLEXPRESS

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.

Set the Service Accounts

On the Server Configuration page, setup shows the account each service will run as. The Database Engine's default is the virtual account NT SERVICE\MSSQLSERVER — 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. Leave the startup types as setup suggests: the engine Automatic, the Agent Manual until you start scheduling jobs.

Choose the Collation Carefully — This One Is Sticky

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. If an application vendor specifies a collation, set it now while it costs nothing.

Set Authentication Mode and the Administrator Logins

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. On the same screen, add the current Windows user (and your admin group) as SQL Server administrators.

Forgetting that last click 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.

Place the Data Files Before the First Database Exists

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, and 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.

Cap the Memory, Then Run the First Checks

SQL Server is designed to use memory aggressively: by default, max server memory is effectively unlimited, so over days it caches data until it holds nearly all the RAM — correct behaviour on a dedicated database server, a nasty surprise on a shared one. The 2022 setup includes a Memory tab: accept its recommended cap, or set your own, leaving roughly 4 GB — or about 20 percent of RAM — for Windows and other applications. The same setting can be changed later from SSMS, as this example for a 16 GB machine shows:

EXEC sp_configure 'max server memory (MB)', 10240;
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 and run the first check:

SELECT @@VERSION;

It should report Microsoft SQL Server 2022. Check in Services that SQL Server (MSSQLSERVER) is Running and set to Automatic, then 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.