database-performancelisted

# Database Performance ## Purpose Turn “the database is slow” into a bounded symptom, a short set of competing mechanisms, and a handoff to the skill that owns the decision. Database incidents cross layers: one endpoint can combine an ORM statement explosion, pool waiting, a stale plan, lock contention, and engine maintenance debt. End this triage stage once an established question has an owner and a bounded next check. Evidence that the existing behavior meets the goal can instead justify no change, with conditions for reopening. ## Triage contract Start with the symptom, time window and known environment; collect only the signals needed to choose the next owner. The packet below is a menu, not a prerequisite to handoff. For greenfield selection, route from requirements and workload evidence without inventing existing engine metrics. Reuse the request, repository, incident packet and prior checks before asking for context. Ask only unresolved questions that change routing, collection or recovery; continue independent work within existing authority. Carry those checks and their limits into the handoff so the specialist does not repeat intake. During an incident, collection must fit the recovery deadline and must not delay already authorized mitigation merely to complete the packet. ```text business symptom, SLO impact, and exact time window: engine, exact version/edition/service tier, topology, and recent changes: operation/query/job and representative parameters/data