RadixTrie-image
SQL Server support

SQL Server support
in South Africa.

Senior SQL Server engineers keep your instances stable, supported and recoverable. Direct access to the person doing the work, with no service desk and no escalation loops.
Founded 2019Randpark Ridge and Stellenbosch24/7 supportSenior DBAs, no service deskVendor neutral
Who this is for

When SQL Server needs a senior owner.

Most SQL Server estates are not broken. They are quietly under-maintained, because the person who knew them has moved on or is stretched across everything else. This service exists for that gap.
  • Businesses running SQL Server in production without a dedicated DBA, or with one who is also the whole infrastructure team.
  • IT managers who want a named senior engineer they can call, rather than a ticket queue.
  • Estates on versions that have left Microsoft's extended support, or with an upgrade or Azure move on the horizon.
  • Teams whose backups have never been proven by restoring them, and who would rather find that out now.
What is covered

Preventative work, actually done.

24/7 support and managed DBA

Monitoring, maintenance, patching and on-call support under one predictable monthly fee, delivered by the engineer who knows your estate.
  • Direct access to a named senior DBA
  • Agreed response commitments, reported against
  • One fixed monthly fee, scope agreed upfront

Backups proven by restores

Backups are verified by restoring them, integrity checks are run, and the recovery time is measured rather than assumed.
  • Restore tests on a schedule
  • Integrity checks and corruption detection
  • Recovery objectives agreed with the business

Performance tuning

Execution plans, blocking and wait statistics reviewed against the real workload, with indexing and configuration tuned rather than left at defaults.
  • Execution plan and wait analysis
  • Index and statistics maintenance
  • Configuration checked, not defaulted

High availability and disaster recovery

Availability groups, failover clustering and log shipping designed around agreed recovery objectives and exercised deliberately.
  • Always On availability groups and clustering
  • Failover tested, not just configured
  • The gap between backup and recovery made explicit

Patching and version lifecycle

A patch cadence that is agreed and kept, and a plan for versions approaching or past the end of Microsoft's extended support.
  • Cumulative updates on an agreed schedule
  • Support status tracked per instance
  • Upgrade paths planned before they become urgent

Upgrades and migrations

Version upgrades, consolidation and moves to Azure with compatibility assessed first, a test environment on the target and a rehearsed cutover.
  • Compatibility assessment before anything moves
  • Query performance compared across versions
  • Rehearsed cutover with a real rollback path
How engagement works

Three steps, no service desk.

STEP 01

Start with a health check

An independent assessment of configuration, capacity, backups, security and version risk, ending in a prioritised list of what to fix first.

STEP 02

Agree the scope and one monthly fee

What we take on and what stays with your team is written down, with response commitments that we report against.

STEP 03

Work with a named senior DBA

You deal directly with the engineer who knows your estate, around the clock, without a service desk between you and the fix.

Proof

SQL Server work we can show.

Client names stay confidential unless a client has agreed otherwise, so our case studies are anonymised. They describe real engagements and the reasoning behind the decisions.
Common questions

Questions we are usually asked.

  • Do you replace our DBA or work alongside them?

    Either. Some clients hand the estate over entirely under a managed DBA agreement; others keep an in-house DBA and use us for senior cover, specific projects or the work that never gets done. The split is agreed upfront and written into the scope.

  • Is support genuinely 24/7?

    Yes. Production support runs around the clock under agreed response commitments, and we report against those commitments rather than asking you to take them on trust.

  • Will we be talking to a service desk?

    No. You deal directly with the senior engineer who knows your environment. There is no escalation loop between you and the person who can fix the problem.

  • We are still on SQL Server 2016 or older. What now?

    SQL Server 2016 left Microsoft's extended support in July 2026, and 2017 follows in October 2027. We assess the estate, rank the options and plan the upgrade or migration before it becomes urgent. Our article on SQL Server 2016 end of support sets out the choices.

  • Do you support SQL Server in Azure?

    Yes. We support SQL Server on premises, on virtual machines and on Azure database services, and we plan and run the move between them when that is the right answer for the workload.

  • How do we start?

    Most engagements start with a health check or a conversation about the estate. Use the form on this page, email expert@radixtrie.com or call +27 63 692 3703 and you will speak to a senior DBA.

Talk to us

Talk to a senior SQL Server DBA.

Tell us a little about the environment: how many instances, which versions, what worries you. A senior SQL Server DBA replies directly, and the first conversation is about understanding your estate, not selling to it.
Prefer email or phone? Write to expert@radixtrie.com or call +27 63 692 3703. Offices in Randpark Ridge, Johannesburg and Stellenbosch.

By submitting this form you agree to our Privacy Policy and consent to being contacted about your enquiry. Conversations stay confidential and focused on your environment.

Further reading

More on SQL Server.