Concept Flow - Data abstraction levels
User View
Logical View
Physical View
Data Storage
Data abstraction in DBMS separates how data is seen by users, how it is logically organized, and how it is physically stored.
0
0
Data abstraction levels in DBMS Theory - Step-by-Step Execution
Execution Sample
DBMS Theory
N/A
This concept shows how data is viewed and managed at different levels in a database system.
Analysis Table
| Step | Abstraction Level | Description | Example | User Interaction |
|---|---|---|---|---|
| 1 | User View (External) | Shows only relevant data to users | A customer sees only their account info | User queries data they need |
| 2 | Logical View (Conceptual) | Defines structure and relationships of all data | Database schema with tables and relations | DBA designs and manages schema |
| 3 | Physical View (Internal) | How data is stored on hardware | Data files, indexes on disk | DBMS manages storage details |
| 4 | Data Storage | Actual bytes on disk or memory | Bits and bytes in storage devices | Invisible to users and admins |
| 5 | End | All levels work together to provide data access | User queries → DBMS translates → storage accessed | System processes user requests |
💡 Process ends after data is retrieved from physical storage and presented at user view.
State Tracker
| Level | Description | Visibility to User | Managed By |
|---|---|---|---|
| User View | Data seen by end users | Visible | DBMS Interface |
| Logical View | Data structure and schema | Hidden | Database Administrator |
| Physical View | Data storage details | Hidden | DBMS Storage Engine |
| Data Storage | Raw data on disk | Hidden | Hardware and OS |
Key Insights - 3 Insights
Why can't users see the physical storage details?
Users only interact with the User View level (see execution_table row 1). Physical storage is complex and managed by the DBMS to simplify user experience.
How does the logical view help in managing data?
Logical view (row 2) defines the structure and relationships, so changes in physical storage don't affect how users see data.
What happens if physical storage changes?
Physical changes are handled internally by DBMS (row 3 and 4), so users and applications continue working without change.
Visual Quiz - 3 Questions
Test your understanding
According to the execution_table, which level shows only the data relevant to a user?
💡 Hint
Check execution_table row 1 for the description of User View.
At which abstraction level does the database schema exist, as per the execution_table?
💡 Hint
Look at execution_table row 2 describing Logical View.
If the physical storage changes, which level ensures users are unaffected?
💡 Hint
Refer to key_moments answer about logical view hiding physical changes.
Concept Snapshot
Data abstraction in DBMS has three main levels: 1. User View: What users see, only relevant data. 2. Logical View: Overall database structure and schema. 3. Physical View: How data is stored on hardware. This separation hides complexity and allows independent changes.
Full Transcript
Data abstraction levels in a database management system separate how data is presented and managed. The User View shows only the data relevant to each user, hiding unnecessary details. The Logical View defines the overall structure and relationships of data, like tables and schemas, managed by the database administrator. The Physical View handles how data is actually stored on disks or memory, managed by the DBMS internally. This layered approach allows users to access data easily without worrying about storage details, and lets the system change storage methods without affecting users or applications.