Support Models
SQL Consultant: What One Does, When to Hire One and How to Scope the Work
What an SQL consultant actually does for SQL Server, Oracle and PostgreSQL, and the signs that it is time to bring one in. How to scope the first engagement, what evidence to switch on beforehand and the questions that show you who is really senior.
Need a hand with this? Talk to a senior database DBA ↓By RadixTrie28 October 20265 min read
An SQL consultant is a senior database specialist you hire for a defined outcome. Typical jobs are fixing slow queries, planning an upgrade or migration, designing high availability, or reviewing an estate that nobody fully understands. Most people who search for one run Microsoft SQL Server. The same work applies to Oracle and PostgreSQL. This guide covers what the work involves, when it pays to bring someone in, and how to set up the first engagement so you get answers, not a report that gathers dust.
What does an SQL consultant do?
The job is diagnosis and decisions, not routine. A good consultant reads the evidence your database already collects, finds the cause and leaves you with changes your team can apply and maintain. The work usually falls into five areas.
- Performance tuning. Find the statements that use the most time, read execution plans, and fix indexing, statistics and query design.
- Upgrades and migrations. Version upgrades, moves to new hardware or the cloud, and platform changes such as Oracle to PostgreSQL.
- High availability and disaster recovery. Design, test and document failover and restores against recovery targets the business has agreed.
- Health checks and audits. Configuration, security, backups, patch levels and capacity, with findings ranked by risk.
- Architecture advice. Schema design, partitioning, consolidation and right-sizing before you buy more hardware or cloud capacity.
SQL consultant, DBA or developer?
A DBA keeps systems running day to day: backups, patching, monitoring and access. A developer writes the application code that sends SQL to the database. A consultant is brought in for a specific problem or decision and works across both sides, reading the developer's queries and the DBA's configuration together. The best consultants have spent years as production DBAs. That background is what makes their advice safe to apply on a live system.
When to bring in a SQL Server consultant (or an Oracle or PostgreSQL one)
These are the situations where outside senior help usually pays for itself:
- Performance has dropped and your team cannot find the cause, or the same fixes keep coming back.
- Your DBA has left, or the database is run by generalists who inherited it.
- An auditor, insurer or board wants evidence that backups restore and failover works.
- You are planning a migration and want an independent view before you commit budget.
- A version you run is at or near the end of support.
On that last point, the dates matter now. SQL Server 2016 extended support ended on 14 July 2026; Microsoft offers Extended Security Updates for up to three more years as a temporary bridge, not a destination. SQL Server 2017 extended support ends on 12 October 2027. PostgreSQL 14 gets its final community release on 12 November 2026. Oracle Database 19c Premier Support runs to 31 December 2029, with paid Extended Support to 31 December 2032.
How to scope the first engagement
Vague briefs produce vague results. Before anyone logs in, agree the following:
- The problem in one sentence, with its business effect. For example: the month-end run now overlaps with morning trading and must finish before it.
- How success is measured. Run time, CPU, recovery time, or a signed-off decision document.
- What is in scope and what is not. Instances, databases, versions and editions.
- Access. Read access to system views and monitoring first, with the least privilege that does the job. Agree a change window if changes are expected.
- The deliverable. Findings ranked by risk and effort, the scripts behind each fix, and a handover session with your team.
- Who applies changes. The consultant, your team or both, always through your change control.
Start small. A fixed-scope review of one critical system quickly shows whether a consultant suits you. Our guide to a database health check explains what that review should cover.
Switch on the evidence before the consultant arrives
Much of the time in a performance engagement goes into gathering history. If the database has been recording what it runs, the consultant starts with weeks of data instead of waiting for the problem to happen again. Each platform has a built-in way to do this.
SQL Server: Query Store
Query Store automatically keeps a history of queries, their plans and runtime statistics. It is not on by default in SQL Server 2016, 2017 or 2019, so check each database. With it, a consultant can see exactly when a plan changed and, where it makes sense, force the earlier plan.
PostgreSQL: pg_stat_statements
The pg_stat_statements module tracks planning and execution statistics for every SQL statement the server runs. It must be added to shared_preload_libraries, which means a server restart. Put that restart in your next maintenance window rather than waiting for the engagement.
Oracle: check your licence before anyone runs AWR
AWR, ASH and ADDM are part of the Diagnostics Pack, an extra-cost option on Enterprise Edition. The CONTROL_MANAGEMENT_PACK_ACCESS parameter defaults to DIAGNOSTIC+TUNING on Enterprise Edition, so the features work whether or not you have paid for them. Tell your consultant what you are licensed for. Without the pack, Statspack is the usual alternative. A senior Oracle consultant asks this question before touching AWR.
Questions that reveal a senior SQL consultant
- Which platforms, versions and editions have you run in production? Edition matters, because features and licensing differ.
- How would you approach our problem on day one? Listen for evidence first: waits, top statements and plans. Be wary of "add more memory" before anyone has looked.
- How do you test a change, and how do you roll it back?
- What will we have when you leave? Expect scripts, documentation and a handover session.
- Who does the work: the senior person you are speaking to, or someone else?
- How do you handle production access and data confidentiality?
If you are comparing firms rather than individuals, our article on choosing a database consultancy covers the wider selection criteria. It is written for South African buyers, but the checks apply anywhere.
One-off SQL consultant or ongoing support?
A consultant suits a defined problem with a clear end. If the same issues keep coming back, or nobody owns the database day to day, the gap is operational and a single project will not close it. That is when a managed or remote DBA service fits better. Many organisations do both: a project to fix and stabilise, then ongoing cover. Managed DBA services explained sets out how that model works.
RadixTrie's senior DBAs consult on SQL Server, Oracle and PostgreSQL from Johannesburg and Stellenbosch, for clients in South Africa and internationally.
Frequently asked questions
What does an SQL consultant do?
They diagnose and fix specific database problems or guide big decisions: performance tuning, upgrades and migrations, high availability and disaster recovery, health checks and architecture. The work covers SQL Server, Oracle and PostgreSQL.
Is an SQL consultant the same as a DBA?
No. A DBA runs the database day to day. A consultant is brought in for a defined problem or decision. Senior consultants have usually worked as production DBAs, which is why their advice is safe to apply.
Can an SQL consultant work remotely?
Yes. Most diagnosis, tuning and planning work only needs secure remote access to the servers and monitoring. Agree the access level and change process before work starts.
How long does an SQL consulting engagement take?
It depends on the scope. A review of one system is much shorter than a migration or a high availability build. Fix the problem statement, the success measure and the deliverable first, and the timeline follows from those.
What should I prepare before hiring an SQL consultant?
A one-sentence problem statement, a list of the systems in scope with versions and editions, read access to monitoring, and history: Query Store on SQL Server, pg_stat_statements on PostgreSQL, and a clear answer on Oracle Diagnostics Pack licensing.
Need a hand with this?
Tell us what you run today and when it has to move. A senior database DBA will reply directly, usually within one working day. Prefer email or phone? Write to expert@radixtrie.com or call +27 10 143 0304, or use the contact page to book a 30-minute call.
TAGSSQL ServerOraclePostgreSQLDatabase ConsultingPerformance TuningDBA