Most Companies Do Not HaveA Data Problem. They HaveA Database Nobody Owns.

Yes, and that is most of this work. We usually start with a health audit so both sides know the actual condition of what we are taking on, rather than discovering it during the first incident.

Monitoring runs continuously, and critical alerts route to an on-call engineer outside office hours rather than into an inbox read the next morning. Response targets are agreed in writing per environment — a production order system and an internal reporting replica do not warrant the same commitment.

Sometimes, but far less often than it is quoted for. A large share of performance problems come down to a missing index, a query written against an assumption that has expired, or a report running on every page load. We profile the real query load first, because that answer is usually cheaper and always more durable.

Rehearsed against a copy before it is run for real, reconciled row-by-row afterwards, with a documented cutover and rollback plan. Migrations fail on the details nobody tested — encoding, collation, timezones, the one table with duplicate keys the old system tolerated — so those get found during the rehearsal.

Yes. We assess what the move actually buys you first, plan the migration path and downtime window, run it as a rehearsed exercise, and verify the result before the old environment is decommissioned.

Yes, and it is included in the managed tier rather than sold as an extra. We restore to a scratch environment on a schedule and record the timing, so your recovery time is a number someone has witnessed rather than one written in a policy document.

A fixed-price assessment covering schema quality, performance, backup and restore viability, replication, security posture, configuration and capacity. You get a prioritised findings register with measured evidence and a remediation plan. Turnaround is typically one to two weeks.

Yes. Data pipelines, warehouse and mart design, dimensional modelling, dashboards and scheduled reporting. Often the highest-value work is simply making data you already hold answerable without someone exporting it to a spreadsheet first.

Yes — duplicate detection and merging, standardisation rules, master data management and reference data alignment, then ongoing data quality rules so it does not silently drift back.

At the database layer, yes: least-privilege access design, privilege audits, encryption at rest and in transit, credential rotation, audit logging, sensitive data discovery, and masking for non-production environments. Broader assessment, penetration testing and incident response sit with our cyber security practice.

Yes, and often that is the arrangement. We can act as the specialist your team escalates to, cover out-of-hours, or take full ownership — whichever fits the gap you actually have rather than the largest contract.

It depends on how many instances and environments there are, the platform mix, data volume and load, your availability target, compliance requirements and the condition of what we are taking over. A health audit is fixed price and is usually the sensible first step, because it also tells us what a retainer should actually cost.

The minimum required for the work, granted by you and revocable at any time. We work under NDA as standard, can operate inside your own cloud accounts and tooling, and everything we configure is documented and handed over.

You keep everything — configuration, documentation, runbooks, monitoring setup and credentials. Nothing we put in place depends on us continuing to be involved, and we hand over to whoever takes it on.