Instance Vs Schema
Duration: 2 min
This video lesson is available to enrolled students.
AI summary & chapters
AI Summary
An AI-generated summary of this video lecture.
This short lecture segment introduces the distinction between a database instance and a schema. The slide titled “Instance and Schemas” defines an instance as the collection of information stored in the database at a particular moment, and the schema as the overall design of the database. The instructor reinforces these definitions with a whiteboard example: an instance is shown as a specific value, such as attribute “a” equal to 2 (written as “inst a = 2”), while the schema is represented by an empty table structure or grid that describes how data is organized. The visual contrast between a concrete stored value and the abstract table layout helps clarify that instances change over time, whereas the schema remains the stable design. The segment is brief and evidence-based; no additional topics are introduced.
Chapters
0:00 – 2:00 00:00-02:00
The slide “Instance and Schemas” presents two definitions: an instance is the collection of information stored at a particular moment, and the schema is the overall design. The instructor then uses the whiteboard to illustrate this with “inst a = 2,” drawing an attribute box labeled “a” with value 2 to represent the instance, and begins sketching a table grid on the right to represent the schema structure.
2:00 – 2:09 02:00-02:09
The final sampled window continues showing the same slide and whiteboard example. The on-screen text still defines instance as information at a particular moment and schema as overall design, while the hand-drawn diagram contrasts the specific value “a = 2” with its corresponding table structure, reinforcing the core distinction.
The central teaching point is that a database schema describes the overall design, while an instance captures the actual data stored at one moment. The instructor supports this with a simple example: “a = 2” as an instance value, and a table grid as the schema. This contrast is useful for revision because it separates static design from dynamic data.