The database went down at 3 a.m. on a Sunday. Who picks up? If your company’s answer is a person’s name (that one person who knows the environment), this guide is for you. We will compare the three DBA support models, without romanticizing any of them, and list what to demand from a provider before signing.
The three DBA support models
1. In-house DBA
A professional (or a team) on your payroll, dedicated to your environment, present in the company culture. It is the model closest to the business, and also the most expensive per working hour: salary, payroll taxes, tools, training and the math nobody does, the cost of vacations, days off and turnover. A single DBA does not cover 24×7: the year has 8,760 hours and their schedule covers about 1,800.
2. Outsourced DBA support (remote DBA)
A managed support contract with a remote DBA: a multi-engine team (Oracle, SQL Server, PostgreSQL, MySQL, MongoDB) on call all year long, with monitoring included and per-severity SLAs. The monthly cost is usually a fraction of an equivalent in-house team, and the coverage is real: late nights, holidays and vacations included. The point to watch is provider quality, and that is exactly what the requirements section below solves.
3. Hybrid model
The in-house team handles the day to day and the bridge to the business; the consultancy covers 24×7 on-call duty, demand spikes and specialties that do not justify a hire (a cloud migration project, heavy performance tuning, a version upgrade). For midsize and large companies, it is often the best cost-benefit: nobody becomes hostage to a single person and the in-house team stops pulling all-nighters.
What to compare beyond price
- Real 24×7 coverage: on-call duty with people actually awake and a real rotation, not a phone ringing into the void
- Multi-engine depth: your estate is rarely a single database engine; support needs to cover them all
- Monitoring included: without monitoring, support only finds out about the incident when a user calls
- Prevention in the contract: tested backups, capacity planning and preventive maintenance, not just firefighting
- Visibility: a monthly executive report and access to what the team did, hour by hour
When in-house makes sense (and when outsourcing pays off)
Keep (or hire) in-house when the database is the company’s own product, when there is constant project volume that keeps a person busy full time, or when compliance rules require your own staff.
Outsource when the environment needs 24×7 coverage a small team cannot deliver, when the company depends on a single person, when incidents keep repeating for lack of prevention, or when the cost of building your own team does not add up. In our services hub we explain how this rationale plays out across our three practice areas.
What to demand from a DBA support provider
- Per-severity SLAs, with response and mobilization times written into the contract
- Direct access to the specialist who solves the problem, without triage layers that only schedule meetings
- A monitoring tool included, with alerts also reaching your team (at Furushima, that role belongs to FuruFlow, with WhatsApp alerts)
- Every activity logged in a ticketing system you can check whenever you want
- A monthly report with what was done, what was prevented and what needs a decision from you
- A continuous improvement plan: support that only reacts is always expensive
- Security and LGPD practices: named accounts, an audit trail and a confidentiality agreement
How much outsourced DBA support costs
The price depends on the number of instances and engines, the criticality (SLA) and the prevention scope contracted. The honest yardstick for comparison is the total cost of your current model: salary and payroll taxes, monitoring tooling, overtime in the middle of the night and the cost of the downtime your current model does not prevent. Want that math for your environment? Talk to a specialist: the first conversation is technical and comes with no strings attached.
O que é um DBA remoto?
É o modelo em que um time de especialistas administra os seus bancos de dados a distância, com monitoramento 24 horas, plantão para incidentes e rotinas preventivas. A empresa mantém o controle dos acessos e recebe relatórios de tudo o que é feito.
Suporte DBA terceirizado funciona para ambientes críticos?
Sim, é justamente onde ele mais se paga: ambientes críticos precisam de cobertura 24 horas, prevenção constante e resposta rápida, o que um time interno pequeno raramente consegue sustentar sozinho o ano inteiro.
Perco o controle do ambiente ao terceirizar o suporte?
Não deve perder: exija acessos nominais, registro de atividades em chamados, relatório mensal e monitoramento com alarmes chegando também no seu time. Fornecedor que resiste a dar visibilidade é sinal de alerta.
Posso terceirizar só uma parte, como o plantão noturno?
Sim. O modelo híbrido é comum: o time interno cuida do horário comercial e a consultoria cobre noites, fins de semana, férias e projetos pontuais como migrações e upgrades.