SQL Server starts and stops after a few seconds: using ERRORLOG, service accounts, master and tempdb
When SQL Server stops during start-up, read ERRORLOG and Windows events first, then check the service account, start-up parameters, system databases, storage and patching.

Establish a factual baseline with “SQL Server ERRORLOG” and “Windows event logs”, then move to “service-account permissions and passwords”. Use instance state, logs, storage and application connectivity as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking SQL Server ERRORLOG, Windows event logs and service-account permissions and passwords independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · SQL Server ERRORLOG | Checking SQL Server ERRORLOG helps establish whether the failing stage is the database instance, connection or application dependency; compare it with a known-good baseline and the incident timeline. | Record the actual state of SQL Server ERRORLOG. Compare SQL and application error logs, instance settings, credentials, client drivers and the actual connection error. |
| 02 · Windows event logs | Checking Windows event logs helps establish whether the failing stage is the database instance, connection or application dependency; compare it with a known-good baseline and the incident timeline. | Record the actual state of Windows event logs. Compare SQL and application error logs, instance settings, credentials, client drivers and the actual connection error. |
| 03 · service-account permissions and passwords | Checking service-account permissions and passwords helps establish whether the failing stage is the database instance, connection or application dependency; compare it with a known-good baseline and the incident timeline. | Record the actual state of service-account permissions and passwords. Compare SQL and application error logs, instance settings, credentials, client drivers and the actual connection error. |
| 04 · startup parameters | Checking startup parameters helps establish whether the failing stage is the database instance, connection or application dependency; compare it with a known-good baseline and the incident timeline. | Record the actual state of startup parameters. Compare SQL and application error logs, instance settings, credentials, client drivers and the actual connection error. |
| 05 · master/model/tempdb paths | Checking master/model/tempdb paths helps establish whether the failing stage is the database instance, connection or application dependency; compare it with a known-good baseline and the incident timeline. | Record the actual state of master/model/tempdb paths. Compare SQL and application error logs, instance settings, credentials, client drivers and the actual connection error. |
| 06 · disk space and patch level | Checking disk space and patch level helps establish whether the failing stage is the database instance, connection or application dependency; compare it with a known-good baseline and the incident timeline. | Record the actual state of disk space and patch level. Compare SQL and application error logs, instance settings, credentials, client drivers and the actual connection error. |
Investigation and change sequence
- Capture a baseline for SQL Server ERRORLOG and Windows event logs and compare it with a known-good system.
- Correlate evidence from service-account permissions and passwords and startup parameters to distinguish the direct fault from dependent symptoms.
- Only if evidence points to master/model/tempdb paths, plan a controlled change with backups, a change window and rollback triggers.
- Finally check disk space and patch level and the real business workflow. Verify sign-in, representative queries and necessary transactions with the application account; inspect both database and application logs.
Validation and rollback evidence
- Verify sign-in, representative queries and necessary transactions with the application account; inspect both database and application logs.
- Recheck master/model/tempdb paths and disk space and patch level against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming SQL Server ERRORLOG is sufficient while overlooking Windows event logs and dependent checks.
- Changing several settings before preserving the original evidence for service-account permissions and passwords.
- A reachable TCP port alone does not prove database login or business application health.
Common questions and acceptance criteria
What should be checked first?
Begin with SQL Server ERRORLOG and Windows event logs. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Verify sign-in, representative queries and necessary transactions with the application account; inspect both database and application logs.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
