In real jobs, DBAs must communicate clearly. Here is the format you will use forever:
Subject: What + where + severity
1) Symptom: What users see
2) Impact: Who/what is affected
3) Evidence: What you measured
4) Action: What you did (or will do next)
5) Status: Current state now
6) Next steps: Prevention / follow-up
Symptom: “Reports timing out in Finance DB.”
Impact: “All finance users unable to run morning report.”
Evidence: “Blocking chain from session 74; long-running transaction holding locks.”
Action: “Coordinated with app team; ended transaction safely.”
Status: “Timeouts stopped; response times normal.”
Next steps: “Add alert on long transactions; review app transaction scope.”
Try it now (5 minutes):
Write a 6-line incident update in your DBA Notebook about a slow query.
Not a member yet? Register now
Are you a member? Login now