02 services / database administration

Your data, fast and safe. Every day, not just on launch day.

I look after SQL Server, PostgreSQL and MySQL estates for teams that cannot afford slow queries or lost data. Performance tuning, migrations, high availability, backups you have actually restored from, and monitoring that tells you before your users do.

A server room aisle lined with equipment racks

// what you get

Deliverables, not deliverable-shaped promises.

  • Health checks with a prioritised, plain-English findings report
  • Query and index tuning with measured before/after numbers
  • Migrations between engines, versions or clouds with minimal downtime
  • High availability and disaster-recovery design, with tested restore drills
  • Backup strategy, retention policy and automated verification
  • Security hardening, access review and audit logging
  • Monitoring, alerting and capacity planning

// typical engagements

Three ways to start.

Starting points, not rigid packages. Every project gets a written scope and a fixed or weekly price before work begins.

1–2 weeks

Health check & tuning

Find out why it is slow and fix the worst offenders.

  • Workload analysis
  • Index & query fixes
  • Config review
  • Written report
Ask about this
from 4 weeks

Migration

Move engines, versions or clouds without losing a row or a weekend.

  • Schema conversion
  • Data validation
  • Rehearsed cutover
  • Rollback plan
Ask about this
monthly

Managed DBA retainer

An experienced DBA on call, without the full-time salary.

  • Monitoring & alerts
  • Monthly review
  • Patch management
  • Priority response
Ask about this

// process

How a database engagement runs.

  1. 01

    Baseline

    Capture the current workload, wait stats and slow queries so improvements are measurable.

  2. 02

    Diagnose

    Separate the real bottlenecks from the noise. Usually a handful of queries cause most of the pain.

  3. 03

    Fix safely

    Changes are tested on a copy, scripted, reviewed and rolled out in a window you choose.

  4. 04

    Verify

    Same measurements again, side by side with the baseline.

  5. 05

    Keep it that way

    Monitoring, runbooks and a maintenance plan so the gains stick.

// related work

Case studies.

All work
Database Logistics · 2025

SQL Server to PostgreSQL migration with near-zero downtime

Moved a logistics company's 400 GB SQL Server estate to PostgreSQL with a rehearsed dual-write cutover, cutting licence costs and unblocking a move to Linux containers.

11 min write freeze at cutover Case study
Database E-commerce · 2024

E-commerce database performance tuning

A three-week performance engagement that took the checkout's slowest query from 2.4 seconds to 180 milliseconds at the 95th percentile, without new hardware.

2.4s → 180ms checkout query, p95 Case study

// tools

What I work with.

SQL ServerPostgreSQLMySQLAlways On AGPatronipgBouncerRedisAzure SQLAWS RDSGrafanaPrometheusPowerShell

// faq

Common questions.

Which databases do you support?

Microsoft SQL Server, PostgreSQL and MySQL/MariaDB, on-premises or in Azure and AWS. I also work with Redis as a caching layer.

Can you work on production systems remotely?

Yes, over VPN or bastion access with least-privilege accounts. Every change is scripted, reviewed and reversible.

We have never tested a restore. Is that bad?

It is common and fixable. A restore drill is part of every engagement; a backup you have not restored is a hope, not a plan.

Do you offer ongoing support?

Yes, through a monthly retainer with monitoring, monthly reviews and priority response for incidents.

How quickly can you start?

A health check can usually begin within a week. Migrations are planned around your release calendar.

Have a project in mind?

Tell me what you are building, what is slow, or what you are raising. I reply to every message personally.