Support Models
Managed DBA Services Explained: What You Hand Over, What You Keep
Managed DBA services are often sold as a black box. This is a plain description of what a managed database service should do for you, what stays your responsibility, and how to tell a good one from a ticket queue.
By RadixTrie3 September 20263 min read
Every organisation with production databases has a DBA. The only question is whether it is a person with the skills and the time, or whether the role has quietly fallen to a developer, a sysadmin or nobody at all. Managed DBA services exist to fill that gap properly. This article explains what a managed database service should include, what remains yours, and how to judge whether a provider is offering expertise or just a queue.
What a managed DBA service does for you
- Watches the estate. Monitoring and alerting for availability, capacity, replication and performance, with a human who knows your systems interpreting the signals.
- Does the preventative work. Backups and restore tests, maintenance jobs, patching, integrity checks and capacity planning, on a schedule, with evidence.
- Responds when it matters. Defined response commitments for incidents, with a senior engineer engaged directly rather than a first-line triage.
- Tunes continuously. Query, index and configuration tuning as a standing activity, so performance problems are found before users find them.
- Plans ahead. Version lifecycles, upgrades, migrations and high-availability design handled as a roadmap rather than as emergencies.
- Reports plainly. A regular health report a non-DBA can read: what changed, what is at risk, what is recommended next.
What you keep
A managed service does not take ownership of your data, your application logic or your business decisions. You still decide recovery objectives (how much data you could afford to lose, and how long you could be down), approve changes and change windows, own the application's schema design and release process, and remain accountable for compliance with laws such as POPIA. A good provider makes those decisions easier by giving you accurate information; it does not make them for you.
Managed service, staff augmentation or break-fix?
There are three common ways to buy database expertise, and they suit different situations.
- Break-fix support is reactive: you call when something is wrong. It is cheap until it is not, and it does none of the preventative work that avoids the call in the first place.
- Staff augmentation places a DBA in your team, on your terms. It works when you have management capacity and a steady workload for one person, and it leaves you exposed when that person is on leave or moves on.
- A managed DBA service gives you a team's coverage and a defined outcome, the health of the database tier, for a predictable fee. It suits organisations whose databases matter more than their headcount allows for.
How to tell a real managed service from a ticket queue
The label is used loosely, so look at the mechanics rather than the brochure:
- Who engages first on a production incident, and how senior are they?
- Is preventative work scheduled and evidenced, or only performed on request?
- Are backups restore-tested, with the results shared with you?
- Is performance tuning included, or quoted as a separate project each time?
- Does the monthly report tell you anything you did not already know?
- Can the provider cover all of your database platforms, so you are not managing three vendors?
- Is the fee fixed and the scope written down?
The simplest test: ask the provider to explain the current top risk in your estate. If the answer is specific and evidenced, you have a managed service. If it is generic, you have a helpdesk.
When a managed DBA service is the right call
It is usually right when production databases are critical but there is no full-time senior DBA; when the estate spans several platforms, for example SQL Server for finance, Oracle for a core system and PostgreSQL for newer applications; when a single in-house DBA is a single point of failure; or when audit, compliance or availability requirements have outgrown informal arrangements. It is usually wrong when the databases are small, non-critical and easily rebuilt, in which case monitoring and tested backups may be all you need.
How RadixTrie delivers managed DBA services
RadixTrie is a South African database specialist with senior engineers across Microsoft SQL Server, Oracle, PostgreSQL and MySQL/MariaDB, with offices in Randpark Ridge and Stellenbosch. Our model is direct access to senior database experts, no service desk and no escalation loops, across all four platforms so that one team owns the database tier. The service covers 24/7 support, managed DBA operations, performance tuning, health checks, upgrades and migrations, high availability and disaster recovery, and security and monitoring. Details are on our <a href="/services">services page</a>, and our <a href="/blog">case studies</a> show the work in practice.
<strong>Related reading:</strong> <a href="/blog/remote-dba-services-south-africa">Remote DBA Services: How Senior Cover Works Across Time Zones and Sites</a> · <a href="/blog/choosing-a-database-consultancy-south-africa">How to Choose a Database Consultancy in South Africa</a> · <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a> · <a href="/blog/sql-server-support-south-africa">SQL Server Support in South Africa: What Good Looks Like</a>
TAGSManaged DBADatabase SupportSQL ServerOraclePostgreSQLSouth Africa