Client stories
What teams report after a review
Names and sectors are used with permission. We include mild reservations where clients offered them.
“The schema review caught a missing composite index on our shipment_events table before Black Friday load testing. Implementation took an afternoon; report latency dropped enough that we postponed a read replica purchase.”
— Nadia P., platform lead, Johannesburg logistics startup
“Clear writing, though I wished the first draft had more MariaDB-specific notes — they amended within two days after we sent our version string.”
— Erik V., DBA, Paarl agricultural co-operative
“SQL performance bundle focused on our top eight BI queries instead of nitpicking ORM-generated noise. The pairing session while we rebuilt one view saved a week of guesswork.”
— Sarah K., head of data, remote-first SaaS with ZA payroll entity
Case note: university research warehouse
A Stellenbosch-adjacent research unit stored longitudinal survey data across seventy-three tables with hand-maintained views. Nexus Schema mapped deprecated rules in legacy rules-based views, proposed a staged migration with parallel write validation, and sat in on two rehearsal cutovers.
Outcome: Production upgrade completed on a Sunday maintenance window with rollback scripts unused. Team cited the ordered risk register as the most valuable artefact for grant auditors asking about data integrity controls.
Case note: retail loyalty rebuild
The client planned to merge three legacy member tables into a single ledger. Our review recommended keeping a narrow archive table for disputed transactions rather than wide soft-delete columns on the hot path.
Outcome: Checkout p95 stayed flat after launch; finance could still trace pre-merge balances through the archive without scanning nullable tombstones.