Oracle Database
Introduction to Databases
What a Database Is
A database is a structured, electronically stored collection of data managed by software that enforces rules, handles multiple users simultaneously, and guarantees that the data you store is the data you get back — exactly, always, without exceptions. The software managing it is called a Database Management System, or DBMS. When it is built on the relational model — tables, rows, columns, and relationships — it is called an RDBMS.
Every table holds one type of thing. A Products table holds products. An Orders table holds orders. A Customers table holds customers. When an order is placed, the Orders table does not copy the customer's details into itself — it simply records the customer's ID and links back to the Customers table. The customer's name, address, and email are stored once and referenced everywhere. This principle — storing each fact in exactly one place — is called normalisation. When a customer changes their address, you update it once and every order linked to them immediately reflects the change.
- A table holds one entity type — Products, Orders, Customers, Employees
- A column defines one attribute every row must provide — Name, Price, OrderDate
- A row is one complete record — one product, one order, one customer
- A primary key uniquely identifies every row in its table — no two rows can share it
- A foreign key links a row to a row in another table — enforced automatically by the database
- Normalisation means storing each fact once and linking to it rather than duplicating it
Where Oracle Fits In
Several RDBMSs exist — MySQL, PostgreSQL, MS SQL Server, and Oracle Database among them. They all speak SQL and follow the same relational principles. What differs is how each one handles scale, concurrency, security, and enterprise-grade reliability.
Oracle Database was the world's first commercially available SQL relational database, released in 1979. In the decades since it has become the enterprise standard for workloads where data integrity, scale, and uptime are non-negotiable. Central banks process millions of transactions through Oracle. Airlines manage seat reservations in Oracle. Tax authorities process hundreds of millions of returns on Oracle. Healthcare networks store patient records that must be instantly available, perfectly accurate, and never lost — in Oracle.
What makes Oracle the choice for these environments is not any single feature — it is the architecture. Oracle was designed from the very beginning for thousands of users reading and writing simultaneously without interfering with each other. Learning Oracle means learning not just how to write queries, but how a serious production database engine actually works from the inside.
- Oracle has been in continuous production use since 1979 — one of the longest track records in enterprise software
- Runs on Linux, Windows, Solaris, and AIX — and as a fully managed service on Oracle Cloud Infrastructure
- Powers the majority of SAP, PeopleSoft, and Oracle E-Business Suite deployments worldwide
- Oracle 23ai is the current release — adding AI and vector search on top of the proven relational engine
ACID — Why You Can Trust a Database
The reason databases are trusted with banking transactions, medical records, and legal filings comes down to four guarantees that every serious relational database makes. These are known as ACID.
Atomicity means a group of operations either all succeed or all fail together. When a bank transfer moves money from one account to another, two things must happen — the debit and the credit. If the server crashes after the debit but before the credit, Atomicity guarantees the debit is automatically undone. No money disappears into a broken state.
Consistency means every operation leaves the database in a valid state. Every rule you have defined — a balance cannot go negative, an order must belong to a real customer, a price must be a positive number — is checked and enforced on every single write.
Isolation means concurrent operations do not interfere with each other. If two customers try to buy the last unit of a product simultaneously, the database handles them in sequence — one succeeds and one gets an accurate response. Oracle's implementation is particularly sophisticated — it gives every running query a consistent snapshot of the data as it was when the query started, so readers and writers never block each other.
Durability means that once a database confirms a transaction is complete, it is permanently saved. Oracle achieves this by writing every change to its redo log before touching the actual data files — so recovery after a crash is a matter of replaying the log, not guessing what was in memory.
- Atomicity — all or nothing, no partial operations ever left in the database
- Consistency — every rule enforced on every write, without exception
- Isolation — concurrent sessions operate independently — Oracle readers never block writers
- Durability — committed data survives crashes and power loss through Oracle's redo log
Lesson Summary
| Concept | What It Means |
|---|---|
| Database | A structured, rule-enforced electronic store of data managed by a DBMS |
| RDBMS | A DBMS built on the relational model — tables, rows, columns, and relationships |
| Primary Key | Uniquely identifies every row in a table — no two rows can share it |
| Foreign Key | Links a row to a row in another table — enforced automatically |
| Normalisation | Storing each fact once and linking to it — no duplication across tables |
| Oracle Database | The world's first commercial SQL RDBMS — enterprise standard since 1979 |
| Atomicity | All operations succeed together or fail together — no partial writes |
| Consistency | Every rule enforced on every write — database never contradicts its own rules |
| Isolation | Concurrent sessions operate independently — Oracle readers never block writers |
| Durability | Committed data survives crashes and power loss — guaranteed by Oracle's redo log |
Practice Questions
Practice 1. What is the principle of storing each fact in exactly one place and linking to it called?
Practice 2. What links a row in one table to a row in another and is enforced automatically by the database?
Practice 3. What does Atomicity guarantee about a transaction that fails halfway through?
Practice 4. What Oracle mechanism writes every change before touching data files, ensuring committed data survives a crash?
Practice 5. Which ACID property ensures that every write leaves the database in a valid state with all rules enforced?
Quiz
Quiz 1. A bank transfer debits one account but the server crashes before crediting the other. What does the database do?
Quiz 2. What is the correct definition of a primary key?
Quiz 3. Two customers try to buy the last product in stock at the exact same moment. Which ACID property ensures only one succeeds correctly?
Quiz 4. A customer changes their address. The database stores it in one place linked to all their orders. How many rows need updating?
Quiz 5. Which ACID property does Oracle's redo log directly implement?
Next up — SQL vs NoSQL Databases — How relational and non-relational databases differ, when each type is the right choice, and where Oracle fits in the modern data landscape.