Database Services

Backups you have actually restored, and queries that stay fast.

The database is usually the one part of a system that cannot be rebuilt from scratch. We set it up, back it up, test the restore, keep it patched and find out why it is slow, whether it runs on your server or in the cloud.

Schedule 1

What is included

  1. D-4.1

    Backups and restore tests

    Automated, encrypted, off-site backups and a scheduled restore test, so you know they work before you need them.

  2. D-4.2

    Performance tuning

    Slow queries found and fixed; indexes and configuration matched to how the application really uses the data.

  3. D-4.3

    Upgrades and migrations

    Version upgrades and moves between servers or into the cloud, rehearsed first, with a rollback plan.

  4. D-4.4

    Monitoring and capacity

    Alerts on replication, disk, connections and errors, and a forecast of when you will run out of room.

  5. D-4.5

    Security and access

    Least-privilege accounts, encrypted connections and an audit of who can read what.

Schedule 2

Typical projects

  • An application that slowed down as the data grew
  • A database nobody has upgraded in years
  • Moving an on-site database to the cloud
  • Proving backups work for an audit

Materials

  • PostgreSQL
  • MySQL
  • MariaDB
  • Microsoft SQL Server
  • SQLite
  • Redis
  • pgBackRest

Schedule 3

How it runs

  1. 01

    Review · first visit

    We look at what is there (network, accounts, devices, servers and backups) and at what is at risk, and you get the findings in writing.

  2. 02

    Plan · in writing

    A prioritised list of fixes with a fixed price for the first set, and a monthly plan if you want ongoing care.

  3. 03

    Fix · scheduled

    Changes made in agreed maintenance windows, outside your working hours where they could interrupt anyone, with a way back for anything risky.

  4. 04

    Document · handover

    Diagrams, an inventory, and admin credentials in your own password manager, so anyone could take over.

  5. 05

    Look after · optional

    Monitoring, patching and support on a monthly plan, or nothing: the documentation means you never need us to keep the lights on.

Schedule 4

Common questions

Can you look after a database another vendor set up?

Yes. We start with a short health check of backups, versions, security and performance, and tell you what we found before taking it on.

Will it need downtime?

Most work does not. Upgrades and migrations that do are scheduled outside your working hours and rehearsed first.

Sheet 09 / 09Next step

Your next system, built for production and yours to keep.

Tell us what you are building. We reply within one business day with questions, a first view of the approach and what a discovery sprint would cover.