The SQL Server Error Log page shows SQL Server error log entries collected for the monitored instance. Use it to troubleshoot server restarts, login failures, database recovery messages, and engine-level warnings.
What To Look For
- SQL Server restarts.
- Database recovery events.
- Login failures.
- Severity errors.
- Availability group messages.
- Backup, restore, or job-related messages.
Workflow
- Open Error Log.
- Filter or scan by time and severity.
- Match messages with alerts or user reports.
- Check Agent Jobs if the message relates to scheduled work.
- Check Always On if the message relates to availability groups.
How To Use SQL Server Error Log Evidence
The SQL Server Error Log is the best place to confirm engine-level events such as restarts, recovery, failed logins, availability group state changes, backup messages, and serious errors. Use it whenever an alert or user report has a specific time window.
Start by filtering around the incident time. A message before the user-visible symptom may be more important than messages after it. Compare error log entries with SQL Server Agent Jobs, SQL Server Always On, SQL Server Alerts, and SQL Server Activity to understand whether the message is cause, symptom, or background noise.
If Mini DBA collection itself is failing, use Service Log for engine-side collection errors. The SQL Server Error Log describes SQL Server events, while Mini DBA logs describe the monitoring service.
SQL Server Error Log FAQ
Why are repeated login failures important?
They can indicate application configuration issues, expired credentials, disabled logins, or security probing.
Does every severity message require action?
No. Interpret severity with timing, recurrence, affected database, and user impact.
What should I capture for support?
Capture the time window, exact message text, affected database or login, related alerts, and recent changes.