Support Models
How to Choose a Database Consultancy in South Africa
The database consultancy you choose will hold the keys to your most important systems. A practical guide to evaluating providers: skills, model, security, references and the contract, with the questions that separate depth from sales.
By RadixTrie3 September 20263 min read
Choosing a database consultancy is a decision about trust as much as skill. Whoever you appoint will have privileged access to the systems your business runs on, and their habits will become your risk profile. This guide sets out how to evaluate providers in the South African market, what to look for, and the questions that reveal whether a firm has real depth or a good brochure.
1. Seniority you can verify
Ask who will actually work on your systems, by name, and what their production experience is on your platforms. Sales engineers and senior people who appear only in the pitch are a warning sign. Ask how the firm handles the loss of an individual: a single expert is a single point of failure, whether they are yours or theirs.
2. Breadth across your actual estate
Most South African organisations run more than one database platform: SQL Server for line-of-business systems, Oracle for a core application, PostgreSQL or MySQL for newer services. A consultancy that covers all of them with genuine depth means one accountable team, one standard and one report. Be wary of a provider that claims every technology equally; ask for specifics on each.
3. A support model, not just a rate card
Understand how incidents actually flow. Who answers, how quickly a senior engineer engages, what happens outside office hours, and what preventative work is included. Our article on <a href="/blog/managed-dba-services-explained">managed DBA services</a> describes the model that keeps estates stable; compare what you are offered against it.
4. Security and POPIA readiness
The provider will process data that includes personal information. Ask how access is granted, controlled, logged and revoked; whether engineers use named accounts and multi-factor authentication; how data leaves your environment, if at all; and whether they expect a written operator agreement as the Protection of Personal Information Act requires. A firm that raises these points unprompted understands the responsibility.
Ask for a sample of their monthly report and a sample restore-test record from an existing client, with identifying details removed. Real providers have both to hand.
5. References and independence
Speak to two or three current clients with estates like yours, and ask about incidents rather than compliments: what went wrong, how the firm responded, and what changed afterwards. Ask also whether the consultancy earns money from reselling licences or hardware; independence matters when the advice is whether to stay on a platform or move.
6. What the contract must say
- Scope: which systems, which platforms, which activities are included and which are quoted separately.
- Response and resolution commitments, by severity, and how they are measured and reported.
- Hours of cover, including public holidays and out-of-hours arrangements.
- Named engineers or the process for changes in staffing.
- Security obligations, access management and the operator agreement.
- Reporting cadence and content.
- Exit: how access is removed, documentation handed over and knowledge transferred if you part ways.
7. The question that reveals the most
Ask the provider to walk through your estate and tell you what they would fix first and why. Depth shows immediately: a specific, prioritised answer grounded in what they observed, versus a generic list. Many good firms will offer a structured <a href="/blog/database-health-check">database health check</a> as the starting point precisely because it produces that answer with evidence.
About RadixTrie
RadixTrie is a South African database specialist with senior engineers across Microsoft SQL Server, Oracle, PostgreSQL and MySQL/MariaDB, and offices in Randpark Ridge and Stellenbosch. Our model is direct access to senior database experts, no service desk and no escalation loops. We publish our approach openly on our <a href="/services">services page</a> and in our <a href="/blog">case studies</a>, and we are happy to be evaluated against every point above.
<strong>Related reading:</strong> <a href="/blog/managed-dba-services-explained">Managed DBA Services Explained: What You Hand Over, What You Keep</a> · <a href="/blog/remote-dba-services-south-africa">Remote DBA Services: How Senior Cover Works Across Time Zones and Sites</a> · <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a>
TAGSDatabase ConsultantsDatabase SupportManaged DBASouth Africa