Syllabus · Guinness World Records 2026

80 HOURS,
HOUR BY HOUR
WHAT YOU WILL LEARN

From the very first idea of computing to administering a production database, taking in SQL, high availability, backup, performance, security, cloud and artificial intelligence along the way.

This page is the official reference for what will be taught in each hour of The Longest Lesson in History. It exists so that you know exactly where you come in, what you will find at each point of the journey and how to plan your attendance. The syllabus starts from zero: no prior knowledge is required.

80H
of uninterrupted teaching
77
hours of content
11
thematic blocks
26
curricular units
When
September 4 to 7, 2026
Where
Três de Maio · RS · Brazil and online
Subject of study
SQL and Database Administration
Official start
Friday, 09:00

The 80 hours, one by one

Use the day filters or the search box to find a specific topic. Times shown are the start of each hour, in Brasília time (UTC−3). The order of the macro topics is deliberately interleaved: the content returns to earlier themes at new levels of depth, a strategy that produces better retention than studying in uniform blocks.

81 entries
Syllabus of the 80 hours: hour, day, start time, macro topic and topic
Hour/ChapterDayStartMacro topicTopic
1 Friday 09:00 Introduction to Computing Introduction to Computing, Computational Thinking and the History of Computing
2 Friday 10:00 Introduction to Databases The Evolution of the Modern Database and Storage Structures
3 Friday 11:00 Introduction to Databases Relational Algebra Operations and Entity-Relationship Diagrams
4 Friday 12:05 Introduction to Databases Entities, Attributes, Relationships, Keys, Integrity Constraints, Uniqueness, Normal Forms
5 Friday 13:05 Introduction to Databases DBMS and ACID; Object Orientation (Abstraction, Inheritance, Encapsulation, Polymorphism); Software Development Life Cycle and Data Modelling
6 Friday 14:05 Introduction to Computing Hardware vs Software; Operating Systems vs Applications; Programming Languages and Platforms
7 Friday 15:10 Introduction to Computing Operating Systems in Practice: Windows vs Linux; Free Software, Open Source, Licences and Community
8 Friday 16:10 Introduction to Computing Hands-On: Installing Oracle Linux on a Virtual Machine
9 Friday 17:10 Introduction to Databases Key Database Technologies, Data Structures and Paradigms
10 Friday 18:15 Introduction to SQL Hands-On: Creating Tables, Populating and Projecting Data, Schemas and Tablespaces; Data Types, Key Modelling and Integrity Constraints
11 Friday 19:15 Introduction to Computing Introduction to Programming, Algorithms, Variables, Conditionals, Functions and Data Structures
12 Friday 20:15 Introduction to Databases Multi-Tier Applications; The Oracle Technology Portfolio; Product Versioning
13 Friday 21:20 Introduction to SQL Introduction to SQL: DDL, DML, DCL, TCL, DQL. SQL Syntax and Transactions
14 Friday 22:20 Introduction to SQL Core Syntax: SELECT; Projecting Columns; Column Lists; Table Structures, Aliasing and Prefixing
15 Friday 23:20 Introduction to SQL Functions and Notation; Arithmetic and Aggregate Operations (Hands-On)
16 Saturday 00:25 Introduction to SQL Simple and Compound Filters; Sorting and Grouping (Hands-On)
17 Saturday 01:25 Introduction to SQL Numeric and String Functions; Format Masks; Type Conversion and Casting
18 Saturday 02:25 Introduction to SQL Conditional Queries: CASE and DECODE; Regular Expressions
19 Saturday 03:30 Introduction to SQL SQL CHALLENGE
20 Saturday 04:30 Introduction to SQL SQL Challenge Review
21 Saturday 05:30 Introduction to Databases Constraints; Views; Materialised Views; Sequences; Types; Auto-increment
22 Saturday 06:35 Introduction to Databases Synonyms; Database Links; Heterogeneous Services and Data Integration
23 Saturday 07:35 Introduction to SQL Set Operations and Subqueries
24 Saturday 08:35 Introduction to SQL Joins (Inner, Left, Right, Full, Cross, Natural) + Antijoins and Semi-Joins
25 Saturday 09:40 Introduction to SQL and Databases Indexes and SQL
26 Saturday 10:40 Introduction to SQL CTEs vs Temporary Tables vs Materialised Views; OVER PARTITION; Compound Inserts
27 Saturday 11:40 Introduction to SQL SQL Performance and Transaction Control: Locks
28 Saturday 12:45 Introduction to Computing Parallel Programming and Parallelism; Classic Problems and Race Conditions
29 Saturday 13:45 Database Administration The Basic Structure of an Oracle Instance; Key Processes and Memory Structures
30 Saturday 14:45 Database Administration Physical Structures and Data Storage in Oracle; Undo and Redo Logs
31 Saturday 15:50 Database Administration Hands-On: Preparing the Server for OUI and GUI; Prerequisites; Compatibility and Technical Documentation
32 Saturday 16:50 Database Administration Hands-On: OUI with a Response File; Optimal Flexible Architecture; Oracle Managed Files
33 Saturday 17:50 Database Administration Hands-On: OUI via the Command Line; Automatic Diagnostic Repository
34 Saturday 18:55 Database Administration Hands-On: Database Configuration Assistant (DBCA); NETCA
35 Saturday 19:55 Database Administration Multitenant Architecture; Startup and Shutdown Modes
36 Saturday 20:55 Database Administration Logs and Diagnostic Files: Alert Logs, Traces, Dumps
37 Saturday 22:00 Database Administration Hands-On: Log Multiplexing; Sizing Redo Logs
38 Saturday 23:00 Database Administration Hands-On: Converting Non-CDB to Multitenant; Cloning PDBs
39 Saturday 00:00 Database Administration Labs on Non-CDB to Multitenant Conversion and PDB Cloning
40 Sunday 01:05 REST
41 Sunday 02:05 High Availability Clustering Fundamentals: Oracle RAC
42 Sunday 03:05 High Availability Standby and Oracle Data Guard; Physical and Logical Standby; DG Broker
43 Sunday 04:05 High Availability Oracle GoldenGate; Oracle Enterprise Manager; Oracle ODI and other tools
44 Sunday 05:10 High Availability Oracle Maximum Availability Architecture (MAA); Resource Manager and Best Practices
45 Sunday 06:10 Database Administration Oracle Versioning and Licensing Basics; Oracle Packs and Options; Certification Paths
46 Sunday 07:10 Database Administration Data and Object Administration: Users; Privileges; Roles; Passwords and Tablespaces
47 Sunday 08:15 High Availability Oracle ASM: Fundamentals; Mirroring and Striping; ASMLib; ASM Filter Driver
48 Sunday 09:15 High Availability Oracle ASM — Installation and Initial Configuration
49 Sunday 10:15 High Availability Oracle ASM — Basic Administration; ASMCMD; Oracle High Availability Services (OHAS)
50 Sunday 11:20 High Availability Oracle ASM — Managing Disks and Diskgroups; Failgroups; KFED; KFOD
51 Sunday 12:20 High Availability Hands-On: ASM Exercises; Installing a Database with ASM
52 Sunday 13:20 High Availability Hands-On: Disk Loss; VM Corruption; Disaster Scenarios
53 Sunday 14:25 High Availability Backup and Disaster Recovery: RPO vs RTO vs SLAs; Introduction to RMAN
54 Sunday 15:25 High Availability Configuring RMAN Backup on the Database and the FRA
55 Sunday 16:25 High Availability Backup Strategies and How to Implement Them
56 Sunday 17:30 High Availability Hands-On: RMAN and Data Loss
57 Sunday 18:30 High Availability DBV; Backup Validation and Other Tools; Recovery Catalog
58 Sunday 19:30 High Availability RMAN: Duplexing; Encryption; Compression; Retention
59 Sunday 20:35 High Availability Other Data Loading Tools: Data Pump; Export/Import; SQL*Loader; and others
60 Sunday 21:35 High Availability Database Jobs; Traces
61 Sunday 22:35 Performance Tuning TKProf and Other Tools for Trace Analysis
62 Sunday 23:40 REST
63 Monday 00:40 Performance Tuning Introduction to Oracle Tuning: OWI; General Concepts and Best Practices
64 Monday 01:40 Performance Tuning Best Practices for Configuring Servers, the OS and Basic Infrastructure
65 Monday 02:40 Performance Tuning Best Practices for Configuring Databases for Performance
66 Monday 03:45 Performance Tuning Common Mistakes and Hands-On
67 Monday 04:45 Performance Tuning Best Practices for Database Modelling
68 Monday 05:45 Performance Tuning Best Practices for Writing SQL
69 Monday 06:50 Performance Tuning Tuning Tools
70 Monday 07:50 Security Database Security: DBSAT, Oracle Auditing, Advanced Security, Label Security, Database Vault and Others
71 Monday 08:50 Security Additional Tools for Database Configuration and Assessment
72 Monday 10:00 Cloud Computing Introduction to Cloud Computing; OCI: Key Components
73 Monday 10:55 Cloud Computing Oracle Database as a Service and Its Specifics
74 Monday 12:00 Cloud Computing Hands-On: Launching an Oracle Instance on the Free Tier
75 Monday 13:00 REST
76 Monday 14:00 Artificial Intelligence Oracle Vector Database
77 Monday 15:00 Artificial Intelligence Oracle Database AI and Best Practices
78 Monday 16:00 Artificial Intelligence Oracle as a Multimodel Database
79 Monday 17:15 Artificial Intelligence Configuring RAG on Oracle Database
80 Monday 18:30 DBA Best Practices and Tuning for AI
81 Monday 19:00 RECORD ESTABLISHED
No entries found with the selected filters.

The three rows marked as rest correspond to the instructor's scheduled breaks, drawn from the rest balance accrued over the course of the attempt. They form part of the official 80-hour count. The schedule may be fine-tuned in order and timing up to the day before the event; any significant changes will be published on this page.

Every hour follows the same 60-minute architecture

Whatever the topic, every hour follows the same structure. Knowing this helps you organise yourself: you know when the explanation comes, when the hands-on work starts and when the clock closes the cycle. The time bands may vary by a few minutes at the instructor's discretion, but the practical activity and the closing quiz are present in every hour.

0 → 6 min
Opening and activation
Picking up the theme of the hour, an opening provocation and a clear statement of the learning objective. Always in dialogue, with a question put to the class.
6 → 32 min
Conceptual development
Interactive exposition, narrated demonstration or code written live, depending on the nature of the content. This is the band in which the instructor-led gamification elements appear.
32 → 52 min
Assessed practical activity
Every hour has a planned activity — hands-on, collaborative or electronic. Corrections are projected, solutions are credited by name and the instructor mediates throughout. Each participant works at their own workstation.
52 → 57 min
Closing and synthesis
Consolidating the concept, linking to the next hour and recording the artefact produced.
57 → 60 min
Multiple-choice quiz · 5 questions in up to 3 minutes
Five multiple-choice questions with four options each, answered individually at your own workstation within three minutes. Marking is automatic and the result appears immediately. It is the record that learning took place in that period.
Theme

Every hour has its own narrative hook

Every hour is anchored in a specific theme — a film or series used as a teaching device. The reference is not decoration: it gives a technical concept a name, an image and a story, and it is what makes a topic covered at 4am still memorable the next day.

The anchor for each hour is not announced in advance. Discovering the reference for each hour is part of the experience.

Practice

There will always be something to do

The activity is the assessment: you demonstrate learning by producing something observable — an SQL script, a configuration file, an execution plan, a concept map, a diagnostic report or a solution built as a group.

  • Individual or paired practice at your own workstation
  • Collaborative activities with defined roles
  • Activities using paper, objects and physical movement in the early hours
Assessment

5 questions at the end of every hour

There are 5 multiple-choice questions per hour, answered within 3 minutes. In some hours the quiz is delivered as a game, keeping the same five questions and the same time limit.

The answers feed a consolidated leaderboard, projected at each curricular-unit changeover and at the closing.

Pace

The time on the clock is a design variable

The schedule runs through three nights, and the design treats fatigue as a parameter, not a surprise. In the overnight windows, short-cycle formats predominate, with movement, cooperative competition and immediate feedback.

Workstation

One computer per participant

Every in-person participant has their own workstation throughout the lesson, with no shared hardware. Pair and group work happens in the discussion and the division of roles — never in sharing a keyboard.

Level

Starts from absolute zero

There are no prerequisites. The first twelve hours assume no familiarity with computing, and the first three do not even require a computer. Those who already have experience will find a challenge from the second block onwards — and in the optional layer described at the end of this page.

What else is worth knowing before you join

The syllabus is organised into two complementary layers: eleven narrative blocks, each with its own identity, and 26 three-hour curricular units — the smallest portion of the lesson that forms a complete learning unit.

Every 3 hours

Curricular units, badges and changeovers

A curricular unit closes every three hours. The changeover is the official moment for participants to join or leave, for a fresh quorum count and for awarding the badge for that unit, with a roll call by name.

  • Anyone who completes the whole journey collects the full set of badges
  • Badges are awarded during the micro-breaks, without interrupting the lesson
  • Digital format guaranteed; physical format subject to sponsorship
Continuity

Stepped out and came back? The lab is waiting for you

Whenever the lab environment changes during a unit, the team publishes a new virtual machine image with the final state of that unit. Anyone who was away restores the image from the immediately preceding point and rejoins the lesson without losing continuity — within ten minutes, with the team's support.

Certification

How long you need to stay

  • In person: 90% of the total time, that is 72 hours, with attendance validated through the official register
  • Online with official validation: 90% of the time, with the camera on, face visible and periodic checks
  • Extension course: 75% of the total time, with a certificate stating the hours completed
  • Up to 8 hours of absence are permitted within the total
Materials

What remains after the event

Registered participants have access to course materials, exercises, labs and support during and after the event. The full recording remains available and the content will be broken into modules and published free of charge, forming a permanent educational archive.

Environments

What you will install and use

  • Oracle Linux on a virtual machine, installed by you in hour 8
  • An Oracle database server, built across hours 31 to 39
  • An SQL client and command-line tools for querying and diagnostics
  • Your own cloud instance, on the free tier, in hour 74
  • A virtual learning environment for materials, quizzes and the leaderboard
Clock

Four counters always visible

Throughout the attempt, four counters remain visible: elapsed time, time remaining to 80 hours, time remaining to the mark being beaten, and the rest-balance panel. In an event of this length, timekeeping is not a detail: it is part of the criteria.

A note on method: the macro topics appear out of strictly linear order in the table. This is intentional. Interleaving topics — and returning to earlier subjects at increasing levels of depth — produces better retention than studying in uniform blocks. If a topic seems to "come back", it is coming back deeper.
Layer 1 · mandatory Layer 2 · optional

For those who want to go further: a parallel layer of gamification

Participants in this lesson will have very different levels of seniority: in the same room there will be people who have never written a line of SQL and people who have been running production databases for ten years. Calibrating the lesson for one group would mean losing the other. That is why, alongside the main lesson, we are proposing a second, optional layer of participation, in a gamified format.

The idea is simple: for those who can handle the core lesson with one hand tied behind their back, offer something that requires both — and of a different nature. Where the main lesson asks you to understand and apply, the parallel layer asks you to devise, design, decide and defend.

Mandatory

LAYER 1 · THE LESSON

The record attempt and the technical training
  • Mandatory participation for all registered students
  • The 80 hours of content on this page
  • A practical activity and a 5-question quiz every hour
  • The basis for certification and for validation with Guinness World Records
Optional

LAYER 2 · THE PARALLEL TRACK

A layer of authored challenges, for anyone who wants it
  • Entirely voluntary, and you can join at any point in the journey
  • Its own separate class in the virtual environment, taking up no lesson time
  • A new challenge released every 3 hours of the lesson
  • Does not affect certification or assessment in the main lesson
  • Anyone who ignores this layer loses absolutely nothing of the lesson
Every 3ha new challenge is released
Timethe earlier you submit, the more you score
Rubricthe quality of the submission earns points
How scoring works

Speed of submission and accuracy

Each challenge opens at a set hour and stays open for a window of time. Scoring combines two axes:

  • Submission time: submitting within the first hours of the window earns a speed bonus; submitting within the window scores in full; after it, you can still submit for reduced points
  • Accuracy rubric: the quality of the submission is assessed against explicit, published criteria, adding points to a valid submission
  • Particularly strong submissions may become permanent course material, credited by name

There is a single score: one leaderboard, fed by the sum of points from all submissions. The more and the better you submit, the more you score.

How to take part

Individually, in your own time

  • Individual participation with asynchronous submissions — informal pairs are allowed
  • Everything happens in the parallel class in the virtual environment, never on stage
  • No challenge can be answered by recognition alone: each one requires you to stop, write, decide and defend
  • AI assistants are not banned — the challenges are built around what cannot be delegated: your own evidence, decisions with a cost, and self-critique

The four criteria of the rubric

Technical depth

Did the person use the concept, or just write its name?

Originality

Does the answer go beyond the obvious and beyond what a search would return?

Feasibility

Would this survive a Monday in production?

Communication

Can someone else understand it without the author explaining?

Tie-breaker, valid for every challenge: between two equivalent submissions, the one that acknowledges its own limitations wins.

And the prize

At the end of the journey there will be a prize for the winner. The format of the prize is still being decided and will be announced before the event begins.

There is a single ranking, and it applies to everyone taking part in this layer.

Important. Layer 2 is not part of the record attempt: it takes up no lesson time, generates no evidence for the Guinness World Records dossier and does not depend on physical attendance. It is a parallel pedagogical layer, open to any interested participant — including those who would not describe themselves as senior. The content of each challenge is revealed only when it is released.

Still have questions about how to take part?

The student FAQ brings together the rules on attendance, rest, presence validation and certification. The registration section on the home page explains the formats available.