Install SQL Server Management Studio (SSMS) on Windows [Guide]

SQL Server Management Studio (SSMS) is Microsoft’s primary tool for managing SQL Server instances, Azure SQL databases, and Azure SQL Managed Instances. It provides a graphical interface for writing T-SQL queries, managing database objects, configuring security, running backups, and monitoring server performance – all from a single application.

Original content from computingforgeeks.com - post 46417

This guide walks through downloading and installing the latest SSMS 22 on Windows, connecting to SQL Server and Azure SQL, creating databases, managing users, running backups, and using productivity shortcuts. We also cover Azure Data Studio as a modern cross-platform alternative. For the official documentation, see the SSMS 22 release notes on Microsoft Learn.

Prerequisites

Before installing SSMS 22, confirm your system meets these requirements:

Operating system – Windows 10 or Windows 11 (64-bit). Windows Server 2016, 2019, 2022, or 2025 are also supported. Arm64 is supported on Windows 11
Processor – x64 or Arm64 CPU. Quad-core or better recommended
RAM – Minimum 4 GB, 16 GB recommended for professional workloads
Disk space – 20 to 50 GB free space depending on features installed. SSD recommended
Display – Minimum 1366 x 768 resolution. 1920 x 1080 or higher recommended
.NET Framework – 4.7.2 or above required to install, 4.8 required to run (installed automatically if missing)
Administrator access – Required for installation
SQL Server instance – A running SQL Server instance (local or remote) to connect to after installation

SSMS 22 connects to SQL Server 2014 (12.x) through SQL Server 2025 (17.x), plus Azure SQL Database, Azure SQL Managed Instance, Azure Synapse Analytics, and SQL databases in Microsoft Fabric.

Step 1: Download SQL Server Management Studio

SSMS 22 uses the Visual Studio Installer instead of a standalone MSI. The download is a small stub installer (vs_SSMS.exe) that bootstraps the full installation.

Download the latest SSMS 22 installer from Microsoft’s official page:

Direct download: https://aka.ms/ssms/22/release/vs_SSMS.exe
Documentation page: Install SQL Server Management Studio – Microsoft Learn

The latest version at the time of writing is SSMS 22.4.1, released on March 18, 2026. Key highlights include GitHub Copilot integration (now GA), Database DevOps workload preview, Object Explorer schema grouping, and vector index support.

You can also install SSMS using the Windows Package Manager from PowerShell or Command Prompt:

winget install Microsoft.SQLServerManagementStudio.22

This pulls the same installer and runs the setup automatically.

Step 2: Install SSMS on Windows

There are two ways to install SSMS – through the graphical installer or silently from the command line. Both produce the same result.

GUI Installation

Double-click the downloaded vs_SSMS.exe file. Accept the User Account Control prompt when it appears. The Visual Studio Installer opens and shows the SSMS installation options.

Accept the license terms – Review the Microsoft Privacy Statement and Software License Terms, then click Continue
Select workloads – The default SSMS workload is pre-selected. Optionally add the Hybrid and Migration workload for migration assessments, or the AI Assistance workload for GitHub Copilot
Individual components – Switch to this tab if you need specific components like the Query Hint Recommendation Tool or SSIS support
Installation location – Change the install path if needed. You can only change the drive on the first install
Click Install – The installer downloads and installs all components. This takes 10-30 minutes depending on your connection speed

After installation completes, launch SSMS from the Start menu by searching for “SQL Server Management Studio 22”.

Silent Installation (Command Line)

For automated deployments or servers without interactive access, run the installer silently from an elevated Command Prompt or PowerShell:

vs_SSMS.exe --quiet --wait

The --quiet flag suppresses all UI, and --wait makes the command block until installation finishes. Add --norestart if you want to prevent automatic restarts:

vs_SSMS.exe --quiet --wait --norestart

To install with a specific language (for example, French):

vs_SSMS.exe --quiet --wait --locale fr-FR

Supported locales include en-us, zh-cn, zh-tw, cs-cz, es-es, fr-fr, de-de, it-it, ja-jp, ko-kr, pl-pl, pt-br, ru-ru, and tr-tr.

After silent installation, verify SSMS is installed by checking the version:

winget list Microsoft.SQLServerManagementStudio.22

The output should show the installed SSMS version number confirming a successful installation.

Step 3: Connect to a SQL Server Instance

Launch SSMS and the Connect to Server dialog opens automatically. Fill in the connection details for your SQL Server instance.

Server type – Database Engine
Server name – Enter the hostname, IP address, or named instance. For a local default instance, use localhost or . (a period). For a named instance, use SERVER\INSTANCENAME
Authentication – Choose Windows Authentication if your Windows account has SQL Server access, or SQL Server Authentication to use a SQL login with username and password
Encryption – Set to Mandatory for production environments. Use Optional for local development if you do not have a certificate configured

Click Connect. If the connection succeeds, Object Explorer loads the server tree showing databases, security, server objects, and other nodes.

If you get a connection error, verify these common issues:

SQL Server service is running – check in services.msc or SQL Server Configuration Manager
TCP/IP protocol is enabled in SQL Server Configuration Manager under SQL Server Network Configuration
Windows Firewall allows port 1433 (TCP) for remote connections
SQL Server Browser service is running if connecting to a named instance (UDP port 1434)

Step 4: Connect to Azure SQL Database

SSMS connects to Azure SQL Database the same way as on-premises SQL Server, with a few differences in authentication.

Server name – Use the full server name from the Azure portal: yourserver.database.windows.net
Authentication – Choose Microsoft Entra MFA (formerly Azure AD) for the most secure option. You can also use SQL Server Authentication if you configured a SQL admin login when creating the Azure SQL server
Database – Optionally specify the database name in the Connection Properties tab. If left blank, you connect to the master database
Encryption – Always set to Strict or Mandatory for Azure SQL

Click Connect. If using Microsoft Entra MFA, a browser window opens for authentication. After signing in, SSMS connects and Object Explorer shows your Azure SQL databases.

Make sure your client IP address is added to the Azure SQL server’s firewall rules. In the Azure portal, navigate to your SQL server, click Networking, and add your public IP under Firewall rules.

Step 5: Create a Database and Tables

With SSMS connected to your SQL Server instance, create a new database. Open a new query window by clicking New Query on the toolbar or pressing Ctrl+N.

Run this T-SQL to create a database:

CREATE DATABASE SampleDB;
GO

Switch to the new database and create a table:

USE SampleDB;
GO

CREATE TABLE Employees (
    EmployeeID INT PRIMARY KEY IDENTITY(1,1),
    FirstName NVARCHAR(50) NOT NULL,
    LastName NVARCHAR(50) NOT NULL,
    Email NVARCHAR(100),
    Department NVARCHAR(50),
    HireDate DATE DEFAULT GETDATE()
);
GO

Insert some sample data to work with:

INSERT INTO Employees (FirstName, LastName, Email, Department)
VALUES 
    ('John', 'Smith', '[email protected]', 'Engineering'),
    ('Sarah', 'Johnson', '[email protected]', 'Marketing'),
    ('Mike', 'Williams', '[email protected]', 'Engineering'),
    ('Lisa', 'Brown', '[email protected]', 'Finance');
GO

Verify the data was inserted correctly:

SELECT * FROM Employees;

The results grid at the bottom of the query window should show all four rows with their auto-generated EmployeeID values and today’s date as HireDate.

You can also create tables visually – right-click Tables under your database in Object Explorer, select New > Table, and use the Table Designer to define columns, data types, and constraints.

Step 6: Run T-SQL Queries in SSMS

The query editor is where you spend most of your time in SSMS. Here are essential query operations every DBA should know.

Filter and sort data with a WHERE clause:

SELECT FirstName, LastName, Department
FROM Employees
WHERE Department = 'Engineering'
ORDER BY LastName;

Check the execution plan before running expensive queries. Press Ctrl+L to display the estimated execution plan, or Ctrl+M to include the actual execution plan when you execute the query. This shows how SQL Server processes the query – look for table scans on large tables that indicate missing indexes.

Use the Activity Monitor to check what is running on the server. Right-click the server name in Object Explorer and select Activity Monitor, or press Ctrl+Alt+A. This shows active sessions, resource waits, and expensive queries in real time.

Query Store is built into SQL Server 2016 and later – it tracks query performance over time. Enable it on your database:

ALTER DATABASE SampleDB SET QUERY_STORE = ON;

After enabling Query Store, find its reports under your database in Object Explorer > Query Store. The Regressed Queries report is particularly useful for identifying queries that got slower after a plan change.

Step 7: Manage Users and Permissions

Security management is a core SSMS function. Create logins at the server level and users at the database level.

Create a SQL Server login:

CREATE LOGIN AppUser WITH PASSWORD = 'StrongP@ssw0rd!2026';
GO

Create a database user mapped to that login and assign a role:

USE SampleDB;
GO

CREATE USER AppUser FOR LOGIN AppUser;
GO

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

The db_datareader role allows SELECT on all tables, and db_datawriter allows INSERT, UPDATE, and DELETE. For tighter control, grant specific permissions instead of roles:

GRANT SELECT, INSERT ON dbo.Employees TO AppUser;
DENY DELETE ON dbo.Employees TO AppUser;
GO

To review what permissions a user has, run this query:

SELECT 
    dp.name AS UserName,
    dp.type_desc AS UserType,
    o.name AS ObjectName,
    p.permission_name,
    p.state_desc AS PermissionState
FROM sys.database_permissions p
JOIN sys.database_principals dp ON p.grantee_principal_id = dp.principal_id
LEFT JOIN sys.objects o ON p.major_id = o.object_id
WHERE dp.name = 'AppUser';

This returns all explicit permissions granted to the user, including the permission state (GRANT, DENY, or REVOKE).

You can also manage security visually – expand Security > Logins in Object Explorer to see all server logins, and Security > Users under each database for database users.

Step 8: Backup and Restore Databases

Regular backups are non-negotiable for any production database. SSMS provides both T-SQL and GUI methods for backup and restore operations.

Run a full database backup using T-SQL:

BACKUP DATABASE SampleDB
TO DISK = 'C:\SQLBackups\SampleDB_Full.bak'
WITH FORMAT, COMPRESSION, STATS = 10;
GO

The FORMAT option overwrites any existing backup in the file. COMPRESSION reduces the backup file size significantly. STATS = 10 prints progress every 10 percent.

Create a differential backup that captures only changes since the last full backup:

BACKUP DATABASE SampleDB
TO DISK = 'C:\SQLBackups\SampleDB_Diff.bak'
WITH DIFFERENTIAL, COMPRESSION, STATS = 10;
GO

For point-in-time recovery, take transaction log backups (requires FULL or BULK_LOGGED recovery model):

BACKUP LOG SampleDB
TO DISK = 'C:\SQLBackups\SampleDB_Log.trn'
WITH COMPRESSION, STATS = 10;
GO

To restore a database from a full backup:

RESTORE DATABASE SampleDB
FROM DISK = 'C:\SQLBackups\SampleDB_Full.bak'
WITH REPLACE, RECOVERY, STATS = 10;
GO

The GUI backup option is also available – right-click the database in Object Explorer, select Tasks > Back Up, choose the backup type (Full, Differential, or Transaction Log), set the destination path, and click OK.

Verify your backups are valid by checking the backup history:

SELECT 
    database_name,
    type AS BackupType,
    backup_start_date,
    backup_finish_date,
    compressed_backup_size / 1048576 AS SizeMB
FROM msdb.dbo.backupset
WHERE database_name = 'SampleDB'
ORDER BY backup_start_date DESC;

This query shows all backup records for the database with timestamps and compressed sizes in megabytes.

Step 9: SSMS Keyboard Shortcuts and Productivity Tips

Knowing keyboard shortcuts makes a real difference when you spend hours in SSMS daily. Here are the ones worth memorizing.

Shortcut	Action
`F5`	Execute the current query or selected text
`Ctrl+N`	Open a new query window
`Ctrl+R`	Toggle the results pane
`Ctrl+L`	Display estimated execution plan
`Ctrl+M`	Include actual execution plan on next execution
`Ctrl+K, Ctrl+C`	Comment selected lines
`Ctrl+K, Ctrl+U`	Uncomment selected lines
`Ctrl+Shift+U`	Convert selected text to uppercase
`Ctrl+Shift+L`	Convert selected text to lowercase
`Ctrl+Alt+A`	Open Activity Monitor
`Alt+F1`	Run sp_help on selected object name
`Ctrl+T`	Results to text mode
`Ctrl+D`	Results to grid mode

Other tips that save time:

Select and execute – Highlight a portion of your query and press F5 to run only the selected text. This is useful for testing individual statements in a large script
Drag objects from Object Explorer – Drag a table or column name from Object Explorer directly into the query editor to insert the fully qualified name
Script objects – Right-click any object in Object Explorer, select Script As, and choose CREATE, ALTER, or DROP to generate the T-SQL script
Template Explorer – Press Ctrl+Alt+T to open Template Explorer with pre-built T-SQL templates for common operations
Code snippets – SSMS 22 includes built-in snippets for creating indexes, managing security objects, and working with AI embeddings. Press Ctrl+K, Ctrl+X to insert a snippet
Export results – Right-click in the results grid to save as Excel, JSON, Markdown, or XML (new in SSMS 22)

Step 10: Install Azure Data Studio as a Modern Alternative

Azure Data Studio is Microsoft’s lightweight, cross-platform database tool that runs on Windows, macOS, and Linux. It does not replace SSMS – it complements it. Use SSMS for full server administration (security, Agent jobs, SSIS, maintenance plans) and Azure Data Studio for query editing, notebooks, and extension-based workflows.

Download Azure Data Studio using winget:

winget install Microsoft.AzureDataStudio

Or download the installer directly from the Azure Data Studio download page.

Key strengths of Azure Data Studio compared to SSMS:

Cross-platform – Works on macOS and Linux, not just Windows
SQL Notebooks – Mix T-SQL, markdown, and results in a single notebook document for runbooks and documentation
Extensions – Add PostgreSQL support, schema compare, database migration tools, and more from the marketplace
Integrated terminal – Run PowerShell or CLI commands without leaving the application
Lighter resource usage – Starts faster and uses less memory than SSMS

Both tools can be installed side by side. Most database professionals keep both – SSMS for administration tasks and Azure Data Studio for day-to-day query work and collaboration.

Conclusion

We installed SQL Server Management Studio 22 on Windows, connected to both local SQL Server and Azure SQL instances, created databases and tables, managed user permissions, and configured backups. SSMS remains the most complete tool for SQL Server administration on Windows.

For production environments, enable dedicated SQL Server listening ports, set up automated backup schedules through SQL Server Agent, configure Always Encrypted for sensitive columns, and monitor query performance with Query Store and the built-in Activity Monitor.