The SQL Server Logins page helps review SQL Server login and security principal information for a monitored instance.
When To Use It
- Reviewing server access.
- Investigating login failures.
- Auditing enabled and disabled logins.
- Checking ownership or security-related configuration.
- Supporting operational handover.
Workflow
- Open Logins for the SQL Server.
- Review login names, types, and status fields.
- Compare with Error Log if login failures are reported.
- Follow internal security review processes before changing access in SQL Server.
How To Review SQL Server Logins
The Logins page provides server-level security context for a monitored SQL Server instance. Use it during access reviews, onboarding, troubleshooting login failures, and operational handover. It helps identify which principals exist at the instance level before you investigate database-specific permissions elsewhere.
For login failure investigations, start with the time and username from the application or user report. Then compare with SQL Server Error Log, which may show failed login messages, disabled login attempts, or authentication-related errors. If a login exists but cannot access a database, continue the investigation in SQL Server permissions and database ownership processes.
Do not change access directly from a monitoring finding without following your security workflow. Record the login, type, status, affected application, and evidence before requesting a change.
SQL Server Logins FAQ
Is a SQL Server login the same as a database user?
No. A login exists at the SQL Server instance level. Database users and permissions are mapped inside individual databases.
Why does a login failure not appear here?
The login list shows principals. Use SQL Server Error Log for failure messages and timing.
Can this page support audits?
Yes. It provides useful inventory context when combined with Reports and your internal access review process.