DBAData and Oracle

In-house or outsourced Oracle DBA: counting the hours you really need

A full-time DBA costs money all year round, while work on Oracle databases comes in waves. How to weigh the real hours, the risks and continuity before you choose in-house, outsourced or both.

Strategic editorial team 13 August 2026 7 min read

Cover: “Oracle DBA: in-house, outsourced or both?”, Data and Oracle

A full-time in-house Oracle database administrator (DBA) makes sense when database work is daily and steady. When the work comes in waves, between upgrades, migrations, period-end closes and emergencies, an outside service often delivers more. So does a mixed formula, with one in-house person for routine work and outside support for projects, peaks and cover. The sums should rest on the real hours, on continuity and on the risk of depending on one person, not on salary alone.

A typical scenario. A company hires an experienced DBA. In normal months, database work takes up part of the week. There are backups to check, the odd slow query to fix and user accounts to manage. The rest of the time goes on tasks that have little to do with the database. Then a migration to a new server and a problem in production arrive together. The same person works twelve-hour days for weeks, alone, because no one else in the company knows how to handle that environment. The problem is not the person. It is that the Oracle workload is not constant, while the cost of an employee is.

What does an Oracle DBA actually do?

The DBA keeps the database behind the ERP, accounting and logistics systems in good health. Oracle’s documentation lists the DBA’s tasks. They include planning and creating databases, managing users and privileges, taking backups, tuning performance and installing the updates released every quarter. In the life of a company, these tasks fall into three groups.

Routine. Space, user accounts, scheduled jobs, error logs, patches and backup checks.
Projects. Version upgrades, migrations, new environments and integrations with other systems.
The unexpected. Sudden slowdowns, hangs, corrupted data, and security or licence audits.

One person is rarely equally expert in performance, backup and continuity, security, licensing and migrations.

Why does Oracle work come in waves?

Because it follows calendars that the company does not control.

Patches. Oracle publishes cumulative fixes every quarter and, since the end of May 2026, security updates in the other months too. Each one has to be tested in a staging environment and applied in production.
Support deadlines. When a version drops out of support, the upgrade becomes a project with a date, as we explained for Oracle databases out of support.
Projects. A server change or a move to the cloud concentrates weeks of intense work, as in migrations with minimal downtime.
The company’s calendar. Year-end closes, seasonal peaks and stocktakes.
The unexpected. A database with corrupted blocks gives no warning.

Which costs matter beyond salary?

The right comparison is not salary against fee. It is between two ways of covering the same work, each with its own cost items.

Item	In-house DBA	Outside service
Base cost	pay and social security contributions, all year round	a fee or hours, according to the contract
Keeping skills up to date	training paid for by the company	paid for by the provider
Holidays, sickness, resignation	a substitute is needed, and often there is none	cover is set by the contract
Out-of-hours work	arrangements and allowances to be agreed	times and hours written into the contract
Knowledge of the environment	often in one person’s head	to be documented and handed over, as a requirement
Recruitment and onboarding	time to search and initial training	start-up and handover time
Control and security	internal access already governed	access to be regulated and logged
Relationship with the rest of the company	daily presence, familiar context	coordination to be organised

The table does not say that one option beats the other. It says that both have hidden costs, and that every one of them has to be laid out.

When does an outside service make sense?

A few critical databases, with work concentrated in certain periods of the year.
Fixed-term projects, such as a migration or a version upgrade. Hiring someone for six months of intense work rarely makes sense.
Several sites or companies that need consistent cover without building an in-house team.
Growing companies that need serious Oracle expertise but not yet a dedicated role.
No internal substitute. If an absence today leaves the database uncovered, continuity is already a problem.

When does an in-house DBA make sense?

The daily work is steady and really does fill a full-time position.
There are many instances, with continuous in-house development and a need for daily presence alongside the developers.
Internal or industry rules require certain access to be reserved for employees.
The database is the heart of the product the company sells, not just of its ERP system.

Does the mixed formula work?

It is often the most robust. The in-house person handles routine work and knows the applications. Outside support steps in for projects, peaks and cover, and brings a periodic review of the environment. That review is a second pair of eyes on configuration, backups and security. The in-house DBA is not left alone at critical moments, and the company does not depend entirely on one person or on one provider.

How do you do the sums in practice?

Count last year’s hours, split between routine, projects and the unexpected. The sources are support tickets, calendars and completed projects.
Write down the downtime you can tolerate. RTO (Recovery Time Objective) is the maximum acceptable downtime. RPO (Recovery Point Objective) is how much data, measured in time, can be lost. Then ask who steps in at night, in the middle of the summer holidays or during a migration.
List the skills you need and mark which ones are covered today.
Compare the full cost of the two routes, using the items in the table.
Read the outside service’s contract before you decide. Look at response times, hours, documentation, access and exit.

What should you ask a provider of outsourced DBAs?

Who works on the database, in which roles, and who covers for whom.
Written response times, by severity and by time of day.
Named, logged access, with a non-disclosure agreement (NDA) and access closed at the end of the engagement. If the provider processes personal data on the company’s behalf, you need a contract that complies with Article 28 of the GDPR.
Documentation handed over, including configurations, procedures and records of restore tests.
Licences respected. No paid feature should be used without cover, not even for a quick diagnosis.
An orderly exit. Agree what the company receives if it changes provider one day.

For companies subject to NIS2, the EU directive on network and information security, there is one more reason. Legislative Decree 138/2024 (Italy’s NIS2 law) requires them to look after security in their relationships with direct suppliers (Article 24(2)(d)). An outside DBA is a supplier with very broad access.

In brief

Oracle work comes in waves. The cost of an employee is constant.
An in-house DBA makes sense with steady daily work, many instances or governance constraints.
An outside service makes sense with a few critical databases, fixed-term projects and no internal substitute.
The mixed formula combines knowledge of the applications with cover for the peaks.
The sums rest on real hours, tolerable downtime, skills and continuity.
With an outside provider, what counts is written response times, logged access, documentation handed over and an orderly exit.

Frequently asked questions

Can an outside DBA work alongside the in-house team?

Yes. Agree in writing who does what. For example, routine work goes to the in-house team, while projects, patches and cover go to the outside provider. Shared procedures stop two people working on the same thing without knowing it.

Can an outside DBA see the company’s data?

Administering a database requires broad access, and that is exactly why the access is regulated before work begins. You need a non-disclosure agreement, named and logged user accounts, connections agreed with IT and no copies of data outside the company without authorisation. Where personal data is involved, you also need the contract required by Article 28 of the GDPR.

Who is liable if the outside service makes a mistake?

The contract decides. It sets out the activities included, response times, responsibilities and limits. That is why the scope is written down before work begins, and every intervention in production is made with a verified backup and a planned fallback.

If you decide to hire, how do you assess a DBA candidate?

Use a technical interview and a test based on real work, both run by someone who administers databases. Qualifications and years of experience alone say little about how a person handles a migration or an emergency.

Administering Oracle databases on an outsourced basis, or alongside the in-house team, is the work of our Oracle & Database Engineering division. We assess the real workload before we propose a one-off intervention or ongoing management. For companies that choose to hire, defining the role and assessing candidates technically is part of our work on critical roles and succession.

Sources

Consulted on 16 September 2026.

Find out moreOracle & Database EngineeringOracle database administration, outsourced or alongside your in-house team. Performance, tested backups, version upgrades and migrations.