Bài 01 :: Tổng quan

Summary

This lesson introduces foundational database concepts, database management systems (DBMSs), their architecture and users, database languages, and common data models.

1. Data, information, databases, and DBMSs

• Data is a formal representation of real-world things or events, such as a student’s name, date of birth, course registration, or a company’s sales figures.
• Information is data that has meaning and helps people understand or manage situations. It supports activities such as administration, learning, and research.
• A database is an organized collection of related data stored for a particular purpose. Examples include databases for managing students, courses, schedules, grades, customers, orders, inventory, and sales.
• A database management system (DBMS) is software that enables users to:
  • Define and maintain databases.
  • Create, add, update, retrieve, and process data.
  • Manage users and grant access permissions.
  • Validate queries and return results to applications and users.

When a query is submitted, the DBMS checks its syntax and whether the requester has permission to perform it. If the query is valid, the DBMS retrieves or changes the relevant data and returns the result.

2. Why database systems are needed

Older file-based approaches often linked applications to separate files. This could lead to storage problems, isolated data, limited sharing, difficult querying, and challenges recovering data after a failure.

Database systems help address concerns such as:

• Reliability and recovery.
• Concurrent access by multiple users or applications.
• Data security and access control.
• Preventing data loss and reducing unnecessary duplication.

3. Database characteristics and views

The lesson highlights several important characteristics:

• Self-description: A database includes metadata describing its structures, data types, storage formats, and constraints. This information is usually kept in a catalog.
• Data independence: Changes to how data is organized should not necessarily require changes to the applications that use it.
• Abstraction: Database design begins with high-level objects, then specifies their attributes and relationships. For example, a student may have an ID, name, gender, birth date, and contact details, and may be related to courses.
• Consistency: Data should be organized to reduce duplication and maintain reliable, coherent records.
• Multiple views: Different users can work with different views of the same database. Finance, logistics, and order-management staff, for example, may each need different information.

4. DBMS architecture and data independence

The architecture is presented in three levels:

• External level: The parts of the database relevant to a particular user or group; other parts can be hidden.
• Conceptual level: A community-wide description of the database, including its data types, relationships, and constraints.
• Internal level: How data is physically organized and stored.

Mappings connect these levels. Their separation supports data independence:

• Logical data independence: Changes to the conceptual structure should not require changes to external views or application programs.
• Physical data independence: Changes to physical storage or organization should not require changes to the conceptual or external levels.

5. Database user groups

The lesson identifies three main user groups:

• Administrators: Manage access and coordinate and monitor database use.
• Designers: Decide what data to store, how to structure it, and which methods or indexes can improve access.
• End users: Retrieve or work with data using applications or other tools suited to their tasks. Developers may also use tools or commands to interact with the database.

6. Capabilities expected of a DBMS

The lecture lists these general capabilities:

1. Data sharing and concurrent access for multiple users or programs.
2. Access control, including permissions for groups and individual users.
3. User interfaces and tools to support database work and data retrieval.
4. Backup and recovery to respond to accidents, errors, or other damaging events.
5. Standards to support consistent database operation and use.

7. Database languages

Four categories of database language are introduced:

• Data Definition Language (DDL): Defines or changes database structures, such as tables and indexes.
• Data Manipulation Language (DML): Queries, inserts, updates, and deletes stored data.
• Transaction Control Language (TCL): Controls transactions, including confirming or reversing changes when needed.
• Data Control Language (DCL): Grants or manages users’ access rights.

8. Data models

Data models can be described at different levels:

• High-level models use concepts familiar to users.
• Implementation or representational models describe data in terms closer to how a computer organizes it.
• Low-level models describe physical storage in greater detail.

The lesson surveys several model types:

• Hierarchical model: Organizes data as a tree, with parent–child relationships. Directory and folder structures are familiar examples.
• Network model: Represents data and relationships as a directed graph, allowing connections beyond a simple tree structure.
• Relational model: Organizes data into relations, commonly represented as tables, using concepts such as attributes, domains, and keys.
• Entity–relationship model: Represents entities, their attributes, and their relationships. It is commonly used in database design.
• Object-oriented model: Uses concepts such as classes, attributes, methods, relationships, events, and inheritance. The lecture describes it as useful for modeling real-world systems and developing software of varying complexity.

Speakers or sources featured

• One instructor or narrator presents the database fundamentals lesson.
• The subtitles do not clearly identify additional speakers or verifiable external sources. Some technical names and terms may be garbled by automatic transcription.