Practice 02
Database management
The database is where outages become expensive. We provide the engineering and operational discipline that keeps critical database estates available, secure and recoverable.
01 / The work
Most incidents are predictable.
An untested backup. A version past end of life. A primary with no failover. A query plan that changed after a statistics update. The work is to find these before they find the business.
We run database estates the way critical infrastructure should be run: with an accurate inventory, tested recovery, controlled change and a small number of people who know exactly what to do when something breaks.
- Estate assessment covering versions, end of life dates, backup integrity, replication lag and single points of failure
- 24/7 monitoring with alert thresholds tied to business impact, not raw CPU graphs
- Backup, point in time recovery and restore drills on a schedule you can audit
- High availability and disaster recovery design with defined RPO and RTO
- Patching and major version upgrades with tested rollback plans
- Query, index and lock tuning for the workloads that actually matter
- Access control, encryption, audit logging and least privilege enforcement
- Runbooks, on-call handover and a monthly service review with evidence
02 / Delivery
From risk register to routine.
- 01
Baseline
We inventory the estate and test what everyone assumes is true: backups, failover, monitoring and access. The gaps become a ranked risk register.
- 02
Stabilize
The highest risk items are fixed first. No optimization program starts before recovery is proven and a restore has been performed.
- 03
Automate
Patching, backup verification and routine checks move into scripts and pipelines. Evidence is retained for audits, not reconstructed later.
- 04
Operate
Monitoring, on-call response, capacity planning and service reviews continue under written targets, with named engineers and a clear escalation path.
03 / What good looks like
Targets we hold ourselves to.
Availability is the headline. Recovery, change safety and toil reduction are what make it sustainable.
Targets agreed with clients at the start of an engagement.
04 / Questions
What clients ask first.
Do you take over existing databases?
Yes. Most engagements begin with a two to three week assessment of the current estate. If the platform is stable, we move into a managed service. If it is not, remediation comes first, with a written plan and an agreed exit condition.
What are your response times?
Targets are severity based and written into the service schedule. For managed estates, critical incidents are acknowledged within 15 minutes, 24 hours a day, with named escalation. Less urgent work follows agreed business hours.
Do you support cloud managed databases?
We support Amazon RDS and Aurora, Azure SQL and Managed Instance, Cloud SQL, and self hosted engines on cloud infrastructure. Managed services still need ownership. We provide it.
Can you cover 24/7 operations?
Yes, through an on-call rotation with documented escalation. Coverage is scoped per estate so you are not paying for idle capacity on systems that do not need it.
How do you handle compliance requirements?
We work to the controls your auditors require and provide evidence for them: access reviews, change records, restore tests, encryption and audit logs. Statquil does not claim certifications it does not hold. If a certification is mandatory, we will tell you before the engagement starts.
05 / Adjacent practices
Where this work connects.
Start here
Let us map your data estate.
A 30 minute call is usually enough to tell whether we are the right team. Bring the constraint that is keeping you up at night.
contact@statquil.com