A SQL Server DBA is responsible for database reliability. Reliability includes:
Prevent downtime
Respond to incidents quickly
Keep services stable
Backups that actually work
Restores that are tested
Point-in-time recovery readiness (when required)
Access control (logins/users/roles)
Least privilege
Auditing and policy discipline
Monitoring CPU/memory/I/O
Identifying slow queries, blocking, deadlocks
Indexing and tuning safely
SQL Server Agent jobs
Maintenance tasks (integrity checks, stats, index strategy)
Alerts and reporting
Operations DBA
backups/restore, jobs, alerts, security basics, maintenance automation
Performance DBA
query plans, indexing, waits, blocking, tempdb, Query Store
Platform DBA
upgrades, migrations, HA/DR, capacity planning, patching
A job-ready DBA can do a little of all three, and is strong in at least one.
Did backups run successfully?
Did any critical jobs fail?
Are there errors in the SQL Server error log?
Is disk space low?
Any blocking storms or deadlocks?
Is anything unusually slow?
Review performance trends
Review job history
Validate at least one restore in a test environment (if possible)
Check growth patterns (data/log/tempdb)
Access review (who should and should not have permissions)
Maintenance review (integrity checks, stats/index strategy)
Patch/upgrade planning (if applicable)
Disaster recovery readiness review
Try it now (5 minutes):
In your DBA Notebook, write:
3 daily checks you will always do
2 weekly checks
1 monthly check
Not a member yet? Register now
Are you a member? Login now