---
title: "Oracle | Skills We Assign For | Azendo"
description: "Oracle Database in enterprise estates — PL/SQL, licensing, migration reality, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/oracle/"
---

[Skills](https://azendo.co/skills/) Data stores and query 

# Oracle.

Oracle Database is an enterprise relational database used where transactional guarantees, scale and vendor support are contractual requirements. It carries deep capability, deep licensing complexity, and a large amount of PL/SQL in most real estates.

## Where Oracle fits on a long engagement.

Oracle estates are defined by their PL/SQL. Decades of business logic sits in packages and procedures, frequently as the only complete statement of how a process actually works, and that is why migration projects off Oracle so reliably exceed their estimates — the database is not storage, it is the application.

Licensing is its own discipline. Processor metrics, options licensed separately, and the audit exposure of using a feature nobody realised was chargeable make cost a design constraint. Teams have incurred substantial unplanned cost by enabling a feature in good faith.

## What an assigned team does with Oracle.

The realistic strategy on most Oracle estates is not migration. It is understanding what is there, documenting the logic, testing it, and modernising around the database rather than replacing it, unless there is a specific commercial trigger.

Saying that plainly, rather than proposing the larger project, is part of how we scope. The reasoning behind that posture is set out in [how we scope and assign](https://azendo.co/why-thailand/).

## What we use Oracle for.

* PL/SQL logic documented and tested Characterisation tests around existing behaviour, so the rules are captured before anything changes.
* Licensing exposure understood Knowing which options are in use and which are chargeable, before an audit establishes it.
* Modernising around rather than through New capability built alongside the database, where replacing it has no business case.

## How Oracle capacity is assigned.

Oracle capacity is assigned under [managed data services](https://azendo.co/services/data-engineering/), starting from an assessment of what the database actually contains rather than from a migration plan.

## Roles we assign Oracle for

* [Database Administrator Data engineering](https://azendo.co/services/data-engineering/database-administrator/)

## Service lines it sits in

* [Data engineering](https://azendo.co/services/data-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in data stores and query

* [SQL — skill we assign for](https://azendo.co/skills/sql/)
* [PostgreSQL — skill we assign for](https://azendo.co/skills/postgresql/)
* [MySQL — skill we assign for](https://azendo.co/skills/mysql/)
* [MongoDB — skill we assign for](https://azendo.co/skills/mongodb/)
* [Snowflake — skill we assign for](https://azendo.co/skills/snowflake/)
* [BigQuery — skill we assign for](https://azendo.co/skills/bigquery/)
* [Redis — skill we assign for](https://azendo.co/skills/redis/)
* [Prisma — skill we assign for](https://azendo.co/skills/prisma/)

## Tell us what your roadmap needs Oracle for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)