Most business applications in Kenya run on MySQL or MariaDB. The database is usually invisible until it becomes slow, corrupt, or too large to back up. By then, the cost of fixing it is much higher than the cost of designing it well.

This guide explains what a MySQL expert does and when to bring one in.

Signs you need one

  • Pages or reports take minutes instead of seconds.
  • The site goes down when traffic increases.
  • Tables have grown into millions of rows without indexes.
  • Backups fail or have never been tested.
  • A crash left the database corrupted.
  • Queries lock each other and transactions time out.

These are database problems, not server problems, and adding more RAM only delays them.

Performance work

A MySQL expert starts with evidence: slow query logs, explain plans, and server metrics. Typical fixes include:

  • Adding the right indexes for the queries the application actually runs.
  • Rewriting queries that scan full tables.
  • Fixing N+1 query patterns in the application.
  • Tuning connection limits, buffers and caching.
  • Archiving old data that nobody reads.

Indexes are the highest-leverage change, but only when chosen from real query patterns. Blindly adding indexes slows writes and wastes disk.

Schema design

Good schema design prevents years of pain:

  • Correct data types and constraints.
  • Normalised where it matters, denormalised where performance requires it.
  • Foreign keys that protect integrity.
  • Charset and collation consistency, especially with older Kenyan applications.
  • A migration process so schema changes are reproducible.

Backups that restore

A backup that has never been restored is a hope, not a backup. A proper setup includes:

  • Automated daily dumps or snapshots.
  • Off-server storage, so a lost hosting account does not lose the data.
  • Retention that matches the business risk.
  • A scheduled test restore to prove it works.

Corruption and recovery

After a crash or a bad migration, recovery means:

  • Stopping writes immediately.
  • Taking a copy of the current data before attempting repair.
  • Using the right recovery tool for the engine (InnoDB vs MyISAM).
  • Rebuilding from a backup if repair would risk data.
  • Reconciling with application logs to find what was lost.

Recovery is stressful precisely because it is usually unplanned. The businesses that suffer least are the ones with tested backups.

What it costs in Kenya

In 2026:

  • Performance audit and tuning: KES 20,000 to 80,000.
  • Schema redesign or migration: varies with application size.
  • Emergency recovery: priced by urgency; can be significant.
  • Ongoing database management: monthly retainer.

The cheapest database work is the design and indexing done before launch. The most expensive is the recovery done after a failure with no backup.

Need this done for you?

MUKI handles website repair, SSL, business email, POS installation, biometric attendance and property software onboarding across Nairobi, Kiambu, Ruiru and Thika.