Lesson 9

This module introduced the foundational structure of relational databases and the vocabulary you need to discuss them clearly. You started with the relational model, learned how data is organized into tables, and then built toward how relational systems connect data across tables and manage change safely over time.

What you learned in this module

1. Relational database structure starts with the relational model

   The relational model provides a formal way to represent data as relations (tables). It is the conceptual foundation that explains why tables work, how they relate, and why set-based querying is possible.

2. Tables, fields, records, and keys are the core building blocks

   A relational database contains multiple tables, where each table represents one subject. Columns (fields) describe that subject, rows (records) represent instances of it, and a primary key uniquely identifies each record.

3. Relational power comes from linking tables

   Tables become more valuable when you can connect them. A foreign key in one table references a primary key in another table, allowing you to retrieve related data using joins while preserving data integrity and reducing redundancy.

4. Relational completeness is a capability benchmark

   Relational completeness is a theoretical measure of whether a language can express the full range of relational queries without relying on procedural loops. It is a useful way to think about expressive power and why relational querying is fundamentally set-based.

5. SQL is the common language of relational databases

   SQL became the lingua franca because it provides a standardized interface for both defining structures (DDL) and manipulating data (DML). While vendors may implement dialect differences, the core concepts transfer across platforms.

6. An RDBMS is the software suite that makes relational databases operational

   An RDBMS packages the database engine and the tooling required to create structures, query data, modify records, enforce security, manage concurrency, and protect data through backup and recovery.

7. Database change management keeps production stable as systems evolve

   Once systems go live, changes must be reviewed, tested, tracked, versioned, and deployed predictably. Change management is how teams avoid ad-hoc edits and maintain reliability as requirements and platforms evolve.

Database Systems

Learning objectives achieved

After completing this module, you should be able to:

1. Describe the relational database model.
2. Describe the structure of a relational database (tables, fields, records).
3. Explain how primary keys and foreign keys link tables to access related data.
4. Explain why SQL became the common language of relational databases.
5. Describe the major functions provided by an RDBMS.
6. Describe the elements of database change management.

Relational model in context

Database models provide different ways to structure and navigate data. In modern systems, the relational model remains the default choice for transactional workloads because it offers strong integrity guarantees, a mature ecosystem, and a proven foundation for set-based querying. Other models (including hierarchical and network approaches) are typically encountered as legacy technologies or specialized implementations.

Object-oriented concepts influenced many products and development styles, but most enterprise systems today still store core business data in relational databases and use object mappings (or service layers) to integrate with application code.

Glossary terms

Before moving on to the next module, click the Quiz link below to check your knowledge of relational database structure and terminology.
Relational Database - Quiz