Profile the real workload
Use evidence from production-like behaviour rather than generic tuning rules.
Database and platform engineering for systems where performance, resilience and data integrity are operational concerns.
Database problems are rarely isolated from the application. Slow queries, locking, growth, backup design and schema changes often surface as user-facing incidents with unclear ownership.
Select each step to see how we would move the work forward without turning it into a larger programme than necessary.
Use evidence from production-like behaviour rather than generic tuning rules.
Prioritise query, schema and configuration changes by business effect.
Test restore and failover assumptions before an incident.
Connect database changes to application release and monitoring practices.
We keep deliverables tied to decisions, delivery and ownership. The exact format changes with the workstream; these are the outputs we would expect to leave behind.
Bring us in when performance incidents recur, growth is exposing capacity limits or recovery assumptions have never been tested properly.
The current problem, the outcome you need and what cannot be disrupted are enough to start.