Logo-Icon
HOMEABOUTSERVICESHOW WE WORKBLOGInstagram-Icon Talk To an Expert
RadixTrie-image
SQL Server support in South Africa
Support Models

SQL Server Support in South Africa: What Good Looks Like

What separates SQL Server support that keeps an estate stable from support that only logs tickets. A practical checklist for South African businesses choosing or reviewing their arrangement.
By RadixTrie3 September 20264 min read
Most SQL Server outages are not surprises. They are the end of a long, quiet run of skipped maintenance: statistics that were never updated, a backup job that has been failing for weeks, a patch that was postponed one more time, a disk that everyone knew was filling up. Good support is the discipline that stops that run before it ends badly. This article sets out what that discipline looks like in practice, so you can judge a support arrangement, whether you are choosing one or reviewing the one you have.

Why the support model matters more than the tooling

Monitoring dashboards, alerting tools and maintenance scripts are table stakes. Every provider has them. What differs is the model around them: who actually looks at the alerts, whether that person understands your systems, how quickly a real engineer engages when something is wrong, and whether anyone is doing the unglamorous preventative work in between incidents.
The most common failure mode we see is not a lack of tools. It is a queue. A ticket is logged, triaged by someone who has never seen the environment, passed to a second line, and eventually reaches a database specialist hours later. By then the business has already felt it. For a production database, the distance between the person who notices the problem and the person who can fix it should be as short as possible.

Five things a good SQL Server support arrangement always includes

  1. Direct access to a senior DBA. Not a service desk, not a call-back promise: a named engineer who knows your estate and answers when it matters.
  2. Preventative maintenance that is actually done. Backups verified by restoring them, integrity checks, index and statistics maintenance, and a patch cadence that is agreed and kept.
  3. Clear ownership. One party accountable for the health of the database tier, with response commitments written down and reported against.
  4. Performance work as part of the service. Slow queries, blocking and poor plans are addressed continuously, not parked until a separate project is approved.
  5. High availability and disaster recovery that have been tested. Availability groups, failover clustering or log shipping are only as good as the last time someone failed over on purpose and timed the recovery.

Backups are not the same as recoverability

Almost every environment has backups. Far fewer have a recent, documented restore test with a measured recovery time. A support arrangement worth paying for treats restore testing as routine work: full and log backups restored to a test instance on a schedule, recovery point and recovery time compared with what the business actually needs, and gaps raised before they matter. If your provider cannot tell you when a backup was last restored successfully, that is the first question to ask this week.

The version question

Support also means knowing where each instance sits in Microsoft's lifecycle. Extended support for SQL Server 2016 ended in July 2026, which means no further security updates for that version. SQL Server 2017 follows in October 2027, and SQL Server 2019 in January 2030. Running a production database past its extended support date is a risk decision, and it should be a conscious one with a plan attached: an in-place upgrade, a migration to a current version, or a move to a managed cloud offering.
If any of your SQL Server instances are on 2016 or earlier, the upgrade conversation is already overdue. Start with an inventory of versions, editions and the applications that depend on each instance.

Performance: the difference between reacting and preventing

SQL Server gives a skilled DBA a lot to work with: execution plans, wait statistics, the Query Store, index usage data and more. The value is in someone reading those signals regularly, spotting the query whose plan regressed after a data change, the index that is being scanned instead of sought, or the blocking chain that appears every month-end. Done continuously, this work is cheap and invisible. Done only after users complain, it is expensive and disruptive.

What to ask before you sign, or renew

  • Who, by name, picks up when we call about a production problem, and what is their experience with SQL Server?
  • How often are our backups restore-tested, and where is the evidence?
  • What does the monthly health report contain, and who reads it with us?
  • How is performance tuning handled: included, or quoted separately each time?
  • How would you scope and run an upgrade off an unsupported version?
  • What happens at two in the morning?
  • Is the fee fixed, and what exactly does it cover?

How RadixTrie supports SQL Server

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 deliberately simple: direct access to senior database experts, no service desk and no escalation loops. For SQL Server that covers 24/7 support, managed DBA services, performance tuning, health checks, upgrades and migrations, high availability and disaster recovery, and security and monitoring. You can read more about each on our <a href="/services">services page</a>.
If you are not sure where your estate stands, a health check is the quickest way to find out. It produces a clear picture of versions, backups, configuration, capacity and risk, and a prioritised list of what to fix first.
<strong>Related reading:</strong> <a href="/blog/sql-server-2016-end-of-support">SQL Server 2016 Is Out of Support: Your Options, Ranked</a> &middot; <a href="/blog/managed-dba-services-explained">Managed DBA Services Explained: What You Hand Over, What You Keep</a> &middot; <a href="/blog/high-availability-disaster-recovery">High Availability and Disaster Recovery: Tested Beats Configured</a> &middot; <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a>
Want a straight answer about your SQL Server environment?
TAGSSQL ServerDatabase SupportManaged DBASouth Africa
RadixTrie-image
SQL Server support in South Africa
Support Models

SQL Server Support in South Africa: What Good Looks Like

What separates SQL Server support that keeps an estate stable from support that only logs tickets. A practical checklist for South African businesses choosing or reviewing their arrangement.
By RadixTrie3 September 20264 min read
Most SQL Server outages are not surprises. They are the end of a long, quiet run of skipped maintenance: statistics that were never updated, a backup job that has been failing for weeks, a patch that was postponed one more time, a disk that everyone knew was filling up. Good support is the discipline that stops that run before it ends badly. This article sets out what that discipline looks like in practice, so you can judge a support arrangement, whether you are choosing one or reviewing the one you have.

Why the support model matters more than the tooling

Monitoring dashboards, alerting tools and maintenance scripts are table stakes. Every provider has them. What differs is the model around them: who actually looks at the alerts, whether that person understands your systems, how quickly a real engineer engages when something is wrong, and whether anyone is doing the unglamorous preventative work in between incidents.
The most common failure mode we see is not a lack of tools. It is a queue. A ticket is logged, triaged by someone who has never seen the environment, passed to a second line, and eventually reaches a database specialist hours later. By then the business has already felt it. For a production database, the distance between the person who notices the problem and the person who can fix it should be as short as possible.

Five things a good SQL Server support arrangement always includes

  1. Direct access to a senior DBA. Not a service desk, not a call-back promise: a named engineer who knows your estate and answers when it matters.
  2. Preventative maintenance that is actually done. Backups verified by restoring them, integrity checks, index and statistics maintenance, and a patch cadence that is agreed and kept.
  3. Clear ownership. One party accountable for the health of the database tier, with response commitments written down and reported against.
  4. Performance work as part of the service. Slow queries, blocking and poor plans are addressed continuously, not parked until a separate project is approved.
  5. High availability and disaster recovery that have been tested. Availability groups, failover clustering or log shipping are only as good as the last time someone failed over on purpose and timed the recovery.

Backups are not the same as recoverability

Almost every environment has backups. Far fewer have a recent, documented restore test with a measured recovery time. A support arrangement worth paying for treats restore testing as routine work: full and log backups restored to a test instance on a schedule, recovery point and recovery time compared with what the business actually needs, and gaps raised before they matter. If your provider cannot tell you when a backup was last restored successfully, that is the first question to ask this week.

The version question

Support also means knowing where each instance sits in Microsoft's lifecycle. Extended support for SQL Server 2016 ended in July 2026, which means no further security updates for that version. SQL Server 2017 follows in October 2027, and SQL Server 2019 in January 2030. Running a production database past its extended support date is a risk decision, and it should be a conscious one with a plan attached: an in-place upgrade, a migration to a current version, or a move to a managed cloud offering.
If any of your SQL Server instances are on 2016 or earlier, the upgrade conversation is already overdue. Start with an inventory of versions, editions and the applications that depend on each instance.

Performance: the difference between reacting and preventing

SQL Server gives a skilled DBA a lot to work with: execution plans, wait statistics, the Query Store, index usage data and more. The value is in someone reading those signals regularly, spotting the query whose plan regressed after a data change, the index that is being scanned instead of sought, or the blocking chain that appears every month-end. Done continuously, this work is cheap and invisible. Done only after users complain, it is expensive and disruptive.

What to ask before you sign, or renew

  • Who, by name, picks up when we call about a production problem, and what is their experience with SQL Server?
  • How often are our backups restore-tested, and where is the evidence?
  • What does the monthly health report contain, and who reads it with us?
  • How is performance tuning handled: included, or quoted separately each time?
  • How would you scope and run an upgrade off an unsupported version?
  • What happens at two in the morning?
  • Is the fee fixed, and what exactly does it cover?

How RadixTrie supports SQL Server

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 deliberately simple: direct access to senior database experts, no service desk and no escalation loops. For SQL Server that covers 24/7 support, managed DBA services, performance tuning, health checks, upgrades and migrations, high availability and disaster recovery, and security and monitoring. You can read more about each on our <a href="/services">services page</a>.
If you are not sure where your estate stands, a health check is the quickest way to find out. It produces a clear picture of versions, backups, configuration, capacity and risk, and a prioritised list of what to fix first.
<strong>Related reading:</strong> <a href="/blog/sql-server-2016-end-of-support">SQL Server 2016 Is Out of Support: Your Options, Ranked</a> &middot; <a href="/blog/managed-dba-services-explained">Managed DBA Services Explained: What You Hand Over, What You Keep</a> &middot; <a href="/blog/high-availability-disaster-recovery">High Availability and Disaster Recovery: Tested Beats Configured</a> &middot; <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a>
Want a straight answer about your SQL Server environment?
TAGSSQL ServerDatabase SupportManaged DBASouth Africa