Three-schema architecture (external, conceptual, internal) in DBMS Theory - Step-by-Step Execution

Concept Flow - Three-schema architecture (external, conceptual, internal)

User View (External Schema)

↓

Community View (Conceptual Schema)

↓

Physical Storage (Internal Schema)

↓

Data Files

Data flows from what users see, through a shared community view, down to how data is physically stored.

Execution Sample

DBMS Theory

User queries -> External schema
External schema maps -> Conceptual schema
Conceptual schema maps -> Internal schema
Internal schema accesses -> Physical storage

Shows how a user query moves through the three layers to access stored data.

Analysis Table

Step	Layer	Action	Result
1	External Schema	User sends query based on personal view	Query received with user-specific format
2	External to Conceptual	Map user query to community data model	Unified query for all users
3	Conceptual to Internal	Translate community model to physical storage details	Access plan for data retrieval
4	Internal Schema	Retrieve data from physical storage	Raw data fetched from disk
5	Internal to Conceptual	Convert raw data to community model format	Structured data ready
6	Conceptual to External	Convert structured data to user view	User-friendly result prepared
7	External Schema	Send result to user	User receives data in expected format

💡 Data successfully retrieved and presented to user through all three schema layers

State Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	Final
Query/Data Format	User format	Community format	Physical storage format	Community format	User format
Data Location	User device	Conceptual model	Disk storage	Conceptual model	User device

Key Insights - 3 Insights

Why do we need three different schemas instead of just one?

Because users see data differently (external), the organization needs a unified model (conceptual), and data must be stored efficiently (internal). See execution_table steps 1, 2, and 3.

How does the system keep user views separate from physical storage details?

By mapping queries and data through the external and conceptual schemas before reaching the internal schema, as shown in execution_table steps 2 and 3.

What happens if the physical storage changes?

Only the internal schema changes; the conceptual and external schemas stay the same, so users are unaffected. This is implied in the separation shown in the concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the user query translated into a community-wide data model?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Action' column in execution_table row for Step 2.

According to variable_tracker, what is the data format after Step 4?

A Physical storage format

B Community format

C User format

D Unchanged

💡 Hint

Look at 'Query/Data Format' variable after Step 4 in variable_tracker.

If the physical storage changes, which schema layer must be updated to keep user views unchanged?

A External schema

B Conceptual schema

C Internal schema

D All three schemas

💡 Hint

Refer to key_moments explanation about physical storage changes.

Concept Snapshot

Three-schema architecture separates DBMS into:
- External schema: user views
- Conceptual schema: unified community model
- Internal schema: physical storage details
This separation allows flexibility and data independence.

Full Transcript

The three-schema architecture organizes database systems into three layers. The external schema is what each user sees, tailored to their needs. The conceptual schema is a unified model representing the entire database for the organization. The internal schema deals with how data is physically stored on disks. When a user sends a query, it passes from the external schema to the conceptual schema, then to the internal schema to access data. The data then flows back through these layers, converting formats at each step, so the user receives data in their expected view. This separation helps keep user views independent from physical storage changes, making the system flexible and easier to maintain.