How to Install SQL Server Management Studio (SSMS) on Windows Server 2022

SQL Server Management Studio (SSMS) is the primary GUI client for administering SQL Server instances, Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics. On Windows Server 2022, SSMS is not bundled with SQL Server itself — it is a free, standalone download that must be installed separately. This article covers downloading SSMS, performing silent enterprise deployments, connecting to SQL instances, and using SSMS features effectively day-to-day.

Downloading SSMS

Microsoft hosts SSMS on the official documentation site. The current GA release as of mid-2026 is SSMS 21.x. The direct installer is named SSMS-Setup-ENU.exe (English) and is approximately 600–750 MB. Download it with PowerShell to avoid browser interaction on a Server Core installation:

$ssmsUrl  = "https://aka.ms/ssmsfullsetup"
$destPath = "C:InstallersSSMS-Setup-ENU.exe"

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Invoke-WebRequest -Uri $ssmsUrl -OutFile $destPath -UseBasicParsing
Write-Host "SSMS installer downloaded to $destPath"

Verify the file hash after download to confirm integrity. Microsoft publishes SHA-256 hashes on the release notes page:

Get-FileHash -Path "C:InstallersSSMS-Setup-ENU.exe" -Algorithm SHA256 | Select-Object Hash

Interactive Installation

Double-click SSMS-Setup-ENU.exe to launch the graphical installer. The wizard presents a single screen with an Install button and an optional path field (default: C:Program Files (x86)Microsoft SQL Server Management Studio 21). Click Install and wait for the progress bar to complete. A reboot is not usually required, but if the Visual C++ Redistributable was updated, a restart prompt will appear.

Silent (Unattended) Installation

For deploying SSMS across multiple servers via Group Policy, SCCM, Intune, or a build script, use the command-line switches:

:: Basic silent install with default path
SSMS-Setup-ENU.exe /install /quiet

:: Silent install with custom path, no restart, write log
SSMS-Setup-ENU.exe /install /quiet /norestart /log "C:LogsSSMS_install.log"

:: Silent install to a custom directory
SSMS-Setup-ENU.exe /install /quiet /norestart ^
    SSMSInstallRoot="D:ToolsSSMS"

Monitor the log file for any errors. A successful installation ends with an exit code of 0. Exit code 3010 means success with a pending reboot. Exit code 1603 indicates a general MSI failure — check that .NET Framework 4.8 or later is present on Windows Server 2022 (it is included by default) and that no earlier SSMS version is in a broken state.

To silently uninstall SSMS:

SSMS-Setup-ENU.exe /uninstall /quiet /norestart

Connecting to a SQL Server Instance

Launch SSMS from the Start menu or by running Ssms.exe. The Connect to Server dialog appears automatically. Fill in:

Server type: Database Engine (default). Choose Analysis Services, Integration Services, or Reporting Services for those workloads.

Server name: The instance name. For the default instance on the local machine, use a period (.) or localhost. For a named instance: WIN2022SQLSQLEXPRESS. For a non-standard port: WIN2022SQL,1434.

Authentication: Windows Authentication uses the currently logged-on Windows account (preferred). SQL Server Authentication requires a SQL login and password. Azure Active Directory options appear for Azure SQL connections.

Click the Options button to reveal additional tabs: Connection Properties (choose a default database), Additional Connection Parameters (set ApplicationIntent=ReadOnly for AG read replicas), and Always Encrypted. Click Connect when ready.

Object Explorer

Object Explorer (View > Object Explorer or F8) is the tree-view panel on the left side of SSMS. It shows all SQL Server instances you are connected to, organized as a hierarchy: Databases, Security, Server Objects, Replication, PolyBase, Always On High Availability, Management, Integration Services Catalogs, and SQL Server Agent. Expand any node to see its children. Right-click a node to see context-specific actions — for example, right-clicking a database reveals options to back up, restore, generate scripts, or view the Detach dialog.

Query Editor

Open a new query window with Ctrl+N or by clicking the New Query button. The Query Editor provides a full T-SQL editing experience. The toolbar shows the current database context (use the dropdown to change it) and connection details. Execute queries with F5 or Ctrl+E. Display the execution plan with Ctrl+L (estimated) or Ctrl+M then F5 (actual). The Results pane below shows grid output, text output, or both.

IntelliSense activates automatically, providing keyword completion, table/column suggestions, and error underlining. If IntelliSense stops responding (common after schema changes), force a refresh with Ctrl+Shift+R.

-- Example: Check which databases have compatibility level below 150 (SQL 2019)
SELECT name, compatibility_level, state_desc, recovery_model_desc
FROM   sys.databases
WHERE  compatibility_level < 150
ORDER BY name;
GO

SQL Server Templates

SSMS ships with a library of T-SQL script templates for common tasks. Open the Template Browser with Ctrl+Alt+T or View > Template Explorer. Templates are organized by category: Database, Index, Stored Procedure, Table, Trigger, View, and many more. Double-clicking a template opens it in a query window with placeholder tokens in angle-bracket format. Press Ctrl+Shift+M to open the Specify Values dialog, which lets you fill in all placeholders at once before running the script.

Exporting and Importing SSMS Settings

SSMS stores settings (fonts, keyboard bindings, environment layout) in %AppData%MicrosoftSQL Server Management Studio21.0. To export settings: Tools > Import and Export Settings > Export selected environment settings > choose a .vssettings output file. Import using the same dialog on a new workstation. This is useful for distributing a standardized configuration across a DBA team, including keyboard shortcuts and editor font sizes.

SSMS Extensions and Azure Data Studio Integration

SSMS supports extensions via the Extensions and Updates menu (Tools > Extensions and Updates in older releases; in SSMS 21 this is integrated into the Extension Manager). The most commonly installed extensions include Redgate SQL Toolbelt components, ApexSQL tools, and the SQL Server Schema Compare extension. The official Microsoft extension for notebook-style querying is Azure Data Studio, which shares some components with SSMS but is a separate product.

Activity Monitor

Activity Monitor (Ctrl+Alt+A or right-click the instance in Object Explorer > Activity Monitor) provides real-time metrics for CPU, waits, data file I/O, recent expensive queries, active processes, and blocked processes. Expand the Processes section to see SPIDs with their status, login, database, and wait type. Right-click a SPID to send a KILL command. The Expensive Queries section lists the top 20 queries by average CPU, elapsed time, I/O, or executions — this is the fastest route to identifying performance problems without writing DMV queries manually.

Configuring SSMS Options

Access all SSMS preferences via Tools > Options. Key settings to configure on a new installation:

Environment > General: Set the startup action to Open Empty Environment (instead of opening Object Explorer automatically) if you prefer a faster launch on a low-memory server.

Query Execution > SQL Server > Advanced: Set SET STATISTICS TIME and SET STATISTICS IO to ON by default so every query automatically reports elapsed time and logical reads in the Messages tab — invaluable for performance tuning.

Query Results > SQL Server > Results to Grid: Enable “Include column headers when copying or saving results” and increase maximum characters retrieved per column from the default 256 to 65535 for NVARCHAR(MAX) and XML columns.

Text Editor > Transact-SQL > Tabs: Set tab size to 4, indent size to 4, and choose Insert Spaces to ensure consistent T-SQL formatting across the team.

Useful SSMS Keyboard Shortcuts

Memorizing these shortcuts dramatically speeds up daily SQL Server administration:

Ctrl+N           -- New Query window
Ctrl+O           -- Open existing .sql file
F5 / Ctrl+E      -- Execute query
Ctrl+L           -- Display estimated execution plan
Ctrl+M           -- Toggle actual execution plan (then F5 to run)
Ctrl+Shift+R     -- Refresh IntelliSense cache
Ctrl+K, Ctrl+C   -- Comment selected text
Ctrl+K, Ctrl+U   -- Uncomment selected text
Ctrl+]           -- Jump to matching parenthesis/BEGIN-END
Ctrl+Shift+M     -- Fill in template parameters
Ctrl+Alt+T       -- Template Explorer
F8               -- Object Explorer focus
Ctrl+R           -- Toggle Results pane
Ctrl+T           -- Results to Text mode
Ctrl+D           -- Results to Grid mode
Alt+F1           -- sp_help on the selected object name
Ctrl+F1          -- sp_helpdb on the selected database name

Connecting to Azure SQL and SQL Managed Instance

SSMS connects to Azure SQL Database and Azure SQL Managed Instance using the same Connect to Server dialog. For Azure SQL Database, use the fully qualified server name (yourserver.database.windows.net) and choose Azure Active Directory — Universal with MFA or SQL Server Authentication. For Azure SQL Managed Instance, use the instance’s private endpoint or public endpoint hostname. The main limitation compared to on-premises: some Object Explorer nodes (such as Server Objects > Linked Servers) may be unavailable because Azure SQL does not expose all server-level features.

-- Verify connection to Azure SQL Database from SSMS query window
SELECT  @@SERVERNAME         AS server_name,
        DB_NAME()            AS current_database,
        SUSER_SNAME()        AS login_name,
        @@VERSION            AS sql_version;
GO

SSMS on Windows Server 2022 is a comprehensive management interface that grows with the complexity of your SQL Server environment. Starting with a silent enterprise deployment ensures every DBA workstation has a consistent, configured baseline, while the full feature set — from Activity Monitor to Template Explorer — makes routine database administration faster and less error-prone.