Core component of SQL Server for storing, processing, and securing data
Hi @Candace Snipes s,
Sharing a general setup path so you have everything in one place. Note that there is no "SSMS 2018" release; the current version is SSMS 22.x and it works with all SQL Server and Azure SQL versions. Download it from the official Microsoft docs page for SQL Server Management Studio.
- Install SSMS Run the installer, keep defaults, restart if prompted.
- Have a database to connect to SSMS is only a client. You need either:
- Azure SQL Database – create one via Azure portal → Create a resource → SQL Database → pick / create a server, database name, and set an admin login + password.
- SQL Server on your machine / network – install SQL Server (Developer or Express edition is free).
- Create the login/user (Azure SQL Database example, SQL Authentication) Connect to the server with the server admin, then in the master database:
CREATE LOGIN app_user WITH PASSWORD = 'StrongPassword!123';
Switch to your database and create the user + grant access:
CREATE USER app_user FOR LOGIN app_user;
ALTER ROLE db_datareader ADD MEMBER app_user; -- read-only
ALTER ROLE db_datawriter ADD MEMBER app_user; -- read/write
-- ALTER ROLE db_owner ADD MEMBER app_user; -- admin on that DB only
- Connect from SSMS Open SSMS → Connect → Database Engine:
- Server name: yourservername.database.windows.net (Azure SQL) or SERVER\INSTANCE (on-prem).
- Authentication: SQL Server Authentication (or Microsoft Entra ID – Password / Interactive if you use Entra).
- Login / Password: the ones you created.
- Click Options → Connection Properties → set Connect to database = your database name.
- First-time firewall (Azure SQL Database only) If you get a firewall error on connect, SSMS will prompt you to sign in with an Azure account and add your client IP automatically, or you can add it from Azure portal → SQL server → Networking → Add your client IPv4 address.
If any part of this doesn't match your setup (on-prem vs Azure, SQL vs Entra auth, or a specific error message), share the exact error and one of us can point at the fix.Hi @Candace Snipes,
Sharing a general setup path so you have everything in one place. Note that there is no "SSMS 2018" release; the current version is SSMS 22.x and it works with all SQL Server and Azure SQL versions. Download it from the official Microsoft docs page for SQL Server Management Studio.
- Install SSMS Run the installer, keep defaults, restart if prompted.
- Have a database to connect to SSMS is only a client. You need either:
- Azure SQL Database – create one via Azure portal → Create a resource → SQL Database → pick / create a server, database name, and set an admin login + password.
- SQL Server on your machine / network – install SQL Server (Developer or Express edition is free).
- Create the login/user (Azure SQL Database example, SQL Authentication) Connect to the server with the server admin, then in the master database:
CREATE LOGIN app_user WITH PASSWORD = 'StrongPassword!123';
Switch to your database and create the user + grant access:
CREATE USER app_user FOR LOGIN app_user;
ALTER ROLE db_datareader ADD MEMBER app_user; -- read-only
ALTER ROLE db_datawriter ADD MEMBER app_user; -- read/write
-- ALTER ROLE db_owner ADD MEMBER app_user; -- admin on that DB only
- Connect from SSMS Open SSMS → Connect → Database Engine:
- Server name: yourservername.database.windows.net (Azure SQL) or SERVER\INSTANCE (on-prem).
- Authentication: SQL Server Authentication (or Microsoft Entra ID – Password / Interactive if you use Entra).
- Login / Password: the ones you created.
- Click Options → Connection Properties → set Connect to database = your database name.
- First-time firewall (Azure SQL Database only) If you get a firewall error on connect, SSMS will prompt you to sign in with an Azure account and add your client IP automatically, or you can add it from Azure portal → SQL server → Networking → Add your client IPv4 address.
If any part of this doesn't match your setup (on-prem vs Azure, SQL vs Entra auth, or a specific error message), share the exact error and one of us can point at the fix.