Unit 1: Database Concepts and Architecture [4 Hours]

A database provides an organized way to store related data, while a Database Management System (DBMS) provides the software needed to create, access, control, and protect that data. This unit explains the people, models, schemas, abstraction levels, languages, interfaces, and architectures that form a complete database system. It also explains how database systems separate users from physical storage so that data can change and grow without forcing every application to be rewritten.

Tested Topics

1. Database users & DBA — 3x (2024, 2024, 2023)
2. Three-schema architecture & data abstraction — 3x (2025, 2023, Model Q)
3. Database languages — 2x (2024, 2023)
4. Client/server database application architecture — 1x (2025)
5. Data independence — 1x (Model Q)
6. Data models — 1x (2023)
7. Schemas and instances — 1x (2025)

1.1 Database

Definition

A database is an organized collection of related data stored so that it can be accessed, managed, updated, and retrieved efficiently.

A database is like an organized digital record room. Instead of keeping student details, fees, courses, and results in unrelated files, the information is kept in a structured collection where related records can be found and updated easily.

Detailed Explanation

Organizations continuously generate data. A college stores student information, a bank records accounts and transactions, a hospital maintains patient records, and an online store keeps product, customer, and order data. When this information becomes large, storing it in separate files creates problems such as duplication, inconsistent values, weak security, and difficult searching.

A database organizes related information according to a predefined structure. In a relational database, information is usually represented through tables containing rows and columns.

• Table: a structured collection of data about one subject, such as Students or Courses.
• Row or record: one complete occurrence of the subject, such as one student.
• Column or attribute: one property of the subject, such as StudentID, Name, or Address.
• Relationship: a connection between data stored in different tables.

For example, a university may maintain a Students table:

The student data can then be related to other tables such as Courses, Enrollments, Fees, and Results. This structure allows the organization to locate information without searching through separate documents manually.

Major Characteristics of a Database

• Related data: stored information normally belongs to a common environment or organization.
• Persistent storage: data remains available after a program ends.
• Structured organization: data follows defined structures and relationships.
• Shared access: multiple authorized users and applications may access the same stored information.
• Controlled modification: changes can be performed systematically instead of editing independent copies.
• Integrated information: related information from different activities can be connected.

1.2 Database Management System (DBMS)

Definition

A Database Management System (DBMS) is software that allows users and applications to define, create, store, retrieve, update, control, and manage a database.

The database contains the information, while the DBMS is the software used to work with that information. Users normally send requests to the DBMS rather than accessing the stored files directly.

Detailed Explanation

A DBMS forms an intermediate layer between users or application programs and stored data. It accepts requests, checks whether the user has permission, interprets the requested operation, performs the required database activity, and returns the result.

The general flow is:

User or application → DBMS → database storage → DBMS → requested result

This arrangement means application developers do not need to know exactly where every byte is stored on a disk. The DBMS handles low-level storage while presenting a more understandable logical structure.

Major Functions of a DBMS

• Database definition: defines tables, fields, relationships, constraints, and other structures.
• Data storage: stores records systematically on secondary storage.
• Data retrieval: finds and returns requested information.
• Data modification: inserts new data, updates existing data, and removes unwanted data.
• Security: controls which users can view or modify particular information.
• Integrity enforcement: applies rules that keep data valid and consistent.
• Concurrency control: coordinates simultaneous access by multiple users.
• Backup and recovery: helps restore data after system errors or failures.
• Metadata management: maintains information describing database structures.
• Transaction management: controls groups of database operations so that data remains consistent.

Database and DBMS Compared

Basic Data Operations

Four common operations performed on database data are known as Create, Read, Update, and Delete (CRUD).

• Create: insert a new record.
• Read: retrieve existing information.
• Update: modify stored information.
• Delete: remove stored information.

For example, using Structured Query Language (SQL), a student record can be retrieved with:

SELECT StudentID, Name, Program
FROM Students
WHERE StudentID = 101;

The DBMS interprets this query, checks the required database structures, retrieves the matching information, and sends the result back to the user or application.

1.3 Database Users and Database Administrator

Definition

Database users are people who interact with a database system for administration, design, programming, data entry, querying, or other activities. A Database Administrator (DBA) is the person or team responsible for the overall control, security, availability, and maintenance of the database system.

Different people use a database in different ways. A DBA manages the system, a designer decides how information should be organized, programmers build applications, and end users use those applications to perform daily tasks.

Detailed Explanation

A database system is not used by one kind of person. Some users work directly with database structures, while others interact through forms, reports, websites, or mobile applications. Understanding these roles explains how responsibilities are divided in a database environment.

1. Database Administrator

The Database Administrator (DBA) has central responsibility for managing the database environment. The DBA does not normally perform every application task. Instead, the DBA ensures that the database remains secure, available, efficient, and recoverable.

Major Roles of a DBA

• Schema definition: creates or coordinates the overall database structure.
• Storage organization: decides or configures how data and supporting files are stored.
• User authorization: creates accounts and grants appropriate permissions.
• Security control: protects confidential data from unauthorized access.
• Integrity management: ensures that database rules and constraints are enforced.
• Backup management: maintains copies required for recovery.
• Recovery management: restores the database after failures.
• Performance monitoring: observes database workload and improves inefficient operations.
• Concurrency management: ensures that simultaneous users do not create inconsistent data.
• Capacity planning: prepares the database for growing amounts of data and users.

2. Database Designers

Database designers identify what information must be stored and determine how that information should be structured. They study organizational requirements and define entities, attributes, relationships, and constraints.

For a university database, a designer may identify Students, Courses, Teachers, Enrollments, and Results as major data objects and then determine how those objects relate to each other.

3. Application Programmers

Application programmers create software that accesses the database. They write programs for activities such as registration, billing, searching, reporting, and transaction processing.

A college registration portal, for example, may contain a form that takes a student's input and sends an SQL statement to the DBMS.

4. End Users

End users use the database to perform their actual work. They may interact through websites, mobile applications, forms, menus, reports, or direct query tools.

Types of End Users

• Naive or parametric users: repeatedly perform predefined operations through fixed forms. Examples include bank tellers, ticket-booking staff, and data-entry operators.
• Casual users: access the database occasionally and may issue different queries depending on current needs. A manager preparing a monthly report is an example.
• Sophisticated users: understand database facilities well and may write advanced queries or perform analysis directly.
• Standalone users: maintain personal databases using ready-made software packages.

5. Specialized Users

Specialized users develop or operate database applications with unusual requirements, such as scientific systems, geographic information systems, engineering applications, multimedia databases, or artificial-intelligence applications.

Comparison of Major Database Users

1.4 Benefits of Databases

Definition

Benefits of databases are the improvements obtained by managing organizational data through a controlled database system instead of keeping independent and unrelated data files.

A database allows information to be shared and controlled from a common system. This reduces duplicated records, makes updates more consistent, strengthens security, and makes large collections of data easier to search and maintain.

Detailed Explanation

1. Controlled Data Redundancy

Data redundancy means unnecessary duplication of the same data. A database can reduce duplication by storing a fact in one appropriate location and allowing other parts of the system to refer to it.

2. Improved Data Consistency

Data consistency means the same fact has compatible values throughout the system. When unnecessary duplicate copies are reduced, contradictory values become less likely.

3. Better Data Sharing

Authorized users from different departments can access a common database. For example, admission, accounts, and examination sections can use the same student identity information while working with different functions.

4. Improved Security

A DBMS allows access rights to be assigned according to user responsibilities. One user may be allowed to view information, another may update it, while confidential information can remain restricted.

5. Enforcement of Data Integrity

Data integrity means data remains valid and accurate according to defined rules. A DBMS can enforce constraints such as unique student identifiers, valid dates, and required values.

6. Backup and Recovery

Database systems can maintain backups and recovery information. If hardware fails or an operation is interrupted, recovery mechanisms help return the database to a consistent condition.

7. Concurrent Access

Multiple users may access a database at the same time. Concurrency-control mechanisms coordinate their operations so simultaneous activities do not corrupt shared information.

8. Better Data Integration

A database brings related information into a coordinated structure. This allows different organizational activities to be connected more effectively than when information is scattered across unrelated files.

9. Data Independence

Database systems can separate applications from many details of data storage and organization. Some database changes can therefore be performed without rewriting every program that uses the data.

10. Centralized Control

Security policies, standards, data definitions, and backup procedures can be managed in a coordinated manner rather than being independently implemented by every application.

Database Approach Compared with Independent File Processing

1.5 Data Models

Definition

A data model is a collection of concepts used to describe the structure of a database, the relationships among data, the constraints on that data, and sometimes the operations used to manipulate it.

A data model gives designers a way to describe what information exists and how pieces of information are connected before concentrating on the exact files and storage locations used by the computer.

Detailed Explanation

Real organizations contain students, customers, products, employees, accounts, transactions, and many relationships among them. A data model provides concepts for representing those objects in an understandable and systematic form.

Data models can be studied according to the level at which they describe the database.

1. Conceptual or High-Level Data Models

A conceptual data model represents data using concepts that closely match the real world. It focuses on what information exists rather than how that information is stored physically.

Common concepts include:

• Entity: a real-world object or concept, such as Student or Course.
• Attribute: a property of an entity, such as StudentName or CourseTitle.
• Relationship: an association among entities, such as a Student enrolls in a Course.

The Entity-Relationship (ER) model is a well-known conceptual data model.

2. Representational or Implementation Data Models

A representational data model describes data in structures that can be understood by users while also being implementable in a DBMS.

Relational Model

The relational model represents data using relations commonly displayed as tables. Rows represent records and columns represent attributes. Relationships are established through matching values such as keys.

Hierarchical Model

The hierarchical model organizes records in a tree structure. Each child normally has one parent, while a parent can have multiple children.

Example:

University → Faculty → Department → Program

Network Model

The network model allows a record to participate in multiple relationships and can represent structures where a child may have more than one parent.

Object-Oriented Model

The object-oriented data model represents information through objects that can contain both data and behavior. It is useful when applications need to manage complex structures more naturally than ordinary rows and columns.

3. Physical or Low-Level Data Models

A physical data model describes how data is represented and stored inside the computer system. It may include record layouts, storage blocks, indexes, file organization, and access paths.

Comparison of Data-Model Levels

1.6 Schemas and Instances

Definition

A database schema is the overall structure or design of a database, while a database instance is the actual data stored in that database at a particular moment.

The schema tells the system what the database is supposed to look like. The instance shows what values are currently inside that structure.

Detailed Explanation

Database Schema

The schema, also called the database's intension, defines the organization of stored data. It includes information such as table names, columns, data types, relationships, and constraints.

For example:

Students(
    StudentID INTEGER,
    Name VARCHAR(100),
    Program VARCHAR(30),
    Semester INTEGER
)

This definition describes the structure of a Students table. It does not tell us which students are currently stored.

Database Instance

The instance, also called the database's extension or state, consists of the actual values stored at a specific time.

If another student is admitted tomorrow, the instance changes. The schema can remain unchanged because the table still has the same columns and rules.

Schema and Instance Compared

1.7 Three-Schema Architecture and Data Abstraction

Definition

The three-schema architecture is a database architecture that separates database descriptions into three levels: the external level, conceptual level, and internal level. Data abstraction means hiding unnecessary lower-level details and showing users only the information needed at their level.

A database contains many details, from user reports down to storage files. The three-schema architecture separates these details so a user does not need to understand physical disk organization, and storage changes do not automatically affect every user view.

Detailed Explanation

The three-schema approach is commonly associated with the American National Standards Institute and Standards Planning and Requirements Committee (ANSI/SPARC) database architecture. It describes how different levels of database representation can be separated.

The levels are arranged as:

External schemas → External-conceptual mapping → Conceptual schema → Conceptual-internal mapping → Internal schema → Physical storage

1. External Level

The external level is the highest level of abstraction. It represents the part of the database that a particular user or group of users needs to see.

Each external representation is called an external schema or user view.

For example:

• A student may see StudentID, Name, Courses, and Grades.
• The accounts section may see StudentID, Name, FeeAmount, and PaymentStatus.
• The examination section may see StudentID, Courses, Marks, and Results.

These users can work with different views even though the information comes from the same underlying database.

2. Conceptual Level

The conceptual level describes the overall logical structure of the entire database. It combines the organization's major data objects, relationships, and constraints without concentrating on physical disk storage.

A university conceptual schema may define:

• Students
• Teachers
• Courses
• Departments
• Enrollments
• Results
• relationships among these structures

There is normally one main conceptual schema for the database.

3. Internal Level

The internal level is the lowest schema level. It describes how data is physically represented and accessed in storage.

It may describe:

• file organization,
• record formats,
• indexes,
• storage blocks,
• access paths,
• record placement.

Most ordinary end users never work directly with these details.

Mappings Between the Levels

The architecture uses mappings to translate requests and results between levels.

External-Conceptual Mapping

The external-conceptual mapping connects each user view to the conceptual database structure. It tells the DBMS how information visible in a particular external view corresponds to the overall logical database.

Conceptual-Internal Mapping

The conceptual-internal mapping connects the logical database structure to the internal storage structure. It tells the system how conceptual objects are represented physically.

How a Request Moves Through the Architecture

Consider a student requesting a result:

Student view requests grade → external schema identifies visible information → conceptual schema identifies the required student, enrollment, and result data → internal mapping locates stored records → DBMS retrieves data → result travels back through the levels → student sees only the permitted view

Why Data Abstraction Is Maintained

Data abstraction reduces complexity by hiding details that are irrelevant to a particular user.

• Reduces complexity: users work with meaningful views instead of storage details.
• Improves security: a user can be shown only required data.
• Supports multiple views: different users can see different portions of the same database.
• Supports data independence: some lower-level changes can be isolated from higher levels.
• Improves maintainability: physical and logical concerns can be handled separately.

Comparison of the Three Levels

1.8 Data Independence

Definition

Data independence is the ability to change the schema at one level of a database system without requiring unnecessary changes to the schema at the next higher level.

Data independence allows database designers to modify certain details of storage or logical organization while keeping programs and user views working with little or no change.

Detailed Explanation

Data independence builds directly on the separation created by the three-schema architecture. Because external, conceptual, and internal descriptions are separated, a modification at one level can sometimes be absorbed through mappings instead of being passed upward to every application.

There are two major types:

1. Physical Data Independence

Physical data independence is the ability to change the internal schema without changing the conceptual schema.

Physical changes may include:

• changing file organization,
• creating or removing indexes,
• changing storage location,
• changing record-placement techniques,
• moving data to different storage hardware.

Example: A DBA creates an index on StudentID to make searches faster. Applications can continue querying StudentID in the same way because the logical structure of the Students table has not changed.

The relationship is:

Internal schema changes → conceptual-internal mapping is adjusted → conceptual schema remains unchanged → external views and applications remain unaffected

2. Logical Data Independence

Logical data independence is the ability to change the conceptual schema without requiring changes to external schemas or application programs that do not depend on the changed part.

Possible logical changes include:

• adding a new attribute,
• adding a new entity or table,
• introducing a new relationship,
• restructuring logical data while preserving existing user views.

Example: A university adds an EmailAddress attribute to the Students structure. An existing application that displays only StudentID and Name may continue functioning without modification.

Physical and Logical Data Independence Compared

1.9 Database Languages and Interfaces

Definition

A database language is a language used to define database structures, retrieve and modify data, control access, and manage database transactions. A database interface is a means through which users or application programs communicate with a DBMS.

Database languages tell the DBMS what operation is required. Interfaces determine how a person or application sends that request, such as through SQL commands, forms, menus, graphical tools, or programming interfaces.

Detailed Explanation

Database work includes several different activities. A designer may need to create a table, a user may retrieve rows, an administrator may grant permission, and an application may save a transaction. Database languages provide statements for these different purposes.

1. Data Definition Language

Data Definition Language (DDL) is used to define and modify database structures such as tables, views, and constraints.

Common DDL operations include:

• CREATE: creates a database object.
• ALTER: changes the structure of an existing object.
• DROP: removes a database object.

Example:

CREATE TABLE Students (
    StudentID INTEGER PRIMARY KEY,
    Name VARCHAR(100),
    Program VARCHAR(30)
);

This statement defines the structure of a Students table.

2. Data Manipulation Language

Data Manipulation Language (DML) is used to retrieve and modify the data stored inside database structures.

Typical operations include:

• INSERT: adds new rows.
• UPDATE: changes existing rows.
• DELETE: removes rows.
• SELECT: retrieves rows.

Examples:

INSERT INTO Students (StudentID, Name, Program)
VALUES (101, 'Asha', 'BBA');

UPDATE Students
SET Program = 'BCA'
WHERE StudentID = 101;

DELETE FROM Students
WHERE StudentID = 101;

SELECT *
FROM Students;

3. Data Query Language

Data Query Language (DQL) is a commonly used practical term for statements that retrieve information, especially the SQL SELECT statement. In many formal classifications, querying is treated as part of DML rather than as a completely separate language category.

Example:

SELECT Name, Program
FROM Students
WHERE Semester = 2;

4. Data Control Language

Data Control Language (DCL) is used to control user privileges and access to database objects.

Common operations include:

• GRANT: gives a user a permission.
• REVOKE: removes a previously granted permission.

Example:

GRANT SELECT ON Students TO report_user;

5. Transaction Control Language

Transaction Control Language (TCL) is used to control transactions and determine whether groups of changes should be permanently saved or undone.

Common operations include:

• COMMIT: permanently saves transaction changes.
• ROLLBACK: cancels applicable uncommitted changes.
• SAVEPOINT: establishes a point inside a transaction to which control may later return.

Example:

UPDATE Accounts
SET Balance = Balance - 500
WHERE AccountID = 1;

UPDATE Accounts
SET Balance = Balance + 500
WHERE AccountID = 2;

COMMIT;

Comparison of Database Languages

Database Interfaces

An interface provides a method for communicating with the database system. Different users require different interfaces because not every user writes SQL directly.

Command-Line Interface

A command-line interface allows users to type database commands directly. It is suitable for administrators, developers, and advanced users who understand the language.

Menu-Based Interface

A menu-based interface provides predefined choices. Users select actions instead of typing commands.

Forms-Based Interface

A forms-based interface presents fields for entering, searching, or updating data. Registration forms and bank transaction screens are common examples.

Graphical User Interface

A Graphical User Interface (GUI) provides windows, icons, visual tables, diagrams, and menus for interacting with database objects.

Web and Mobile Interfaces

Websites and mobile applications can communicate with databases through application software. The user sees pages and forms while the application sends database operations behind the interface.

Programming Interfaces

Programs may communicate with databases through interfaces such as Open Database Connectivity (ODBC) or Java Database Connectivity (JDBC). These mechanisms allow application code to establish database connections and execute database commands.

Natural-Language and Specialized Interfaces

Some systems allow users to express requests using natural language or domain-specific tools. The interface then converts the request into operations understood by the database system.

1.10 Database System Environment

Definition

A database system environment is the complete set of hardware, software, data, procedures, people, and interfaces that work together to store, process, manage, and use database information.

A database does not operate alone. Servers provide computing resources, DBMS software manages stored information, people perform different roles, procedures define how work is done, and applications provide useful access to the data.

Detailed Explanation

1. Hardware

Hardware includes the physical equipment on which the database system runs.

Examples include:

• database servers,
• client computers,
• storage devices,
• memory,
• network equipment,
• backup devices.

2. Software

Software includes the programs required to operate and use the database.

It may include:

• the DBMS,
• operating system,
• application programs,
• database utilities,
• network software,
• development tools.

3. Data

Data is the central resource being stored and managed. A database environment contains both operational data and information describing that data.

Metadata means data about data. For example, a definition stating that StudentID is an integer and must be unique is metadata.

Metadata is often maintained in a data dictionary or system catalog.

4. Procedures

Procedures are documented methods and rules for operating the database environment.

They may cover:

• how users receive accounts,
• how backups are taken,
• how failures are handled,
• how changes are approved,
• how security incidents are managed,
• how applications are deployed.

5. People

The environment contains users such as DBAs, designers, programmers, operators, analysts, and end users. Their responsibilities were discussed in 1.3 Database Users and Database Administrator.

6. Interfaces and Applications

Interfaces and applications provide usable ways for people or other programs to communicate with the DBMS. A student portal, accounting application, reporting system, or administrative dashboard may all use the same underlying database.

How the Environment Works Together

A typical database operation may follow this sequence:

User enters data in an application → application sends a request → DBMS validates and processes the request → DBMS accesses database files through the operating system → result is returned to the application → user receives output

Security rules, metadata, and database procedures influence this process throughout the environment.

Components Compared

1.11 Centralized and Client/Server Architectures for DBMSs

Definition

A centralized database architecture keeps the main database and database-processing facilities at a central computer or site. A client/server architecture divides database application work between client machines that request services and server machines that provide shared services such as database processing.

In a centralized system, most resources are concentrated at one location. In client/server systems, user-facing work can occur on clients while database services are handled by one or more servers connected through a network.

Detailed Explanation

Centralized DBMS Architecture

In a centralized DBMS, the database is stored and primarily managed at a central site. Users may access the system through terminals or connected computers, but the central machine performs the main database processing.

Typical flow:

User terminal → central computer running application and DBMS → centralized database storage → result returned to user

Advantages of Centralized Architecture

• Central administration: database policies can be controlled from one location.
• Consistent security management: access policies are easier to coordinate centrally.
• Simplified backup: the main data is concentrated at one site.
• Reduced data duplication: users access a common database.

Limitations of Centralized Architecture

• Central failure risk: failure of the central system can affect many users.
• Processing bottleneck: heavy demand may overload the central computer.
• Network dependency for remote users: users at other locations depend on connectivity to the central site.

Client/Server DBMS Architecture

A client is a computer or application that requests a service. A server is a computer or process that provides a shared service.

In a database environment:

• the client may handle the user interface,
• the server runs the DBMS,
• the server processes database requests,
• the server sends results back to the client.

Typical flow:

Client application sends request → database server processes query → server accesses database → server returns result → client displays output

Two-Tier Database Application Architecture

In a two-tier architecture, the client application communicates directly with the database server.

The two tiers are:

1. Client tier: user interface and often some application logic.
2. Database-server tier: DBMS and stored database.

Flow:

User → client application → database server → database → database server → client application → user

For example, a desktop inventory application can connect directly to a database server through an appropriate database driver.

Characteristics of Two-Tier Architecture

• Client communicates directly with the DBMS.
• Suitable for smaller controlled environments.
• Application logic may be stored partly on each client.
• Database connection details must be managed on client systems.
• A large number of direct clients can increase server connection load.

Three-Tier Database Application Architecture

In a three-tier architecture, an intermediate application server is placed between the client and database server.

The tiers are:

1. Presentation tier: user interface on a browser, desktop program, or mobile application.
2. Application tier: business logic, validation, authentication, and processing.
3. Data tier: DBMS and database storage.

Flow:

User → presentation tier → application server → database server → application server → presentation tier → user

Worked Example: Online Result System

Consider a university result website.

1. A student enters a symbol number in the browser.
2. The browser sends the request to the web or application server.
3. The application server validates the input and checks access rules.
4. The application server sends a query to the database server.
5. The DBMS retrieves the corresponding result.
6. The database server sends the data back to the application server.
7. The application server prepares the response.
8. The browser displays the result to the student.

The student's browser does not connect directly to the database. The middle tier handles application rules and protects the database from direct client access.

Two-Tier and Three-Tier Compared

Centralized and Client/Server Compared

1.12 Classification of Database Management Systems

Definition

Classification of Database Management Systems means grouping DBMSs according to characteristics such as their data model, number of users, distribution of data, architecture, and intended purpose.

Not every DBMS organizes or deploys data in the same way. Some use tables, some use tree or object structures, some run at one site, and others operate across multiple computers. Classification helps describe these differences clearly.

Detailed Explanation

A DBMS can be classified using more than one basis. The same DBMS may therefore belong to several categories at the same time.

1. Classification According to Data Model

Hierarchical DBMS

A hierarchical DBMS organizes records in a tree-like parent-child structure. Each child normally has one parent.

Example structure:

Company → Department → Employee

Network DBMS

A network DBMS represents data using records and links that allow more complex many-to-many relationships than the basic hierarchical structure.

Relational DBMS

A Relational Database Management System (RDBMS) organizes data into relations commonly represented as tables. Relationships are established using common values and keys.

Examples include MySQL, PostgreSQL, Oracle Database, and Microsoft SQL Server.

Object-Oriented DBMS

An Object-Oriented Database Management System (OODBMS) stores data in the form of objects and supports object-oriented concepts useful for complex application structures.

Object-Relational DBMS

An Object-Relational Database Management System (ORDBMS) extends relational concepts with support for more complex or object-oriented data features.

NoSQL DBMS

Not Only SQL (NoSQL) is a broad category of database systems designed around non-relational models such as document, key-value, wide-column, and graph structures. These systems are commonly used when an application's data shape, scale, or access requirements do not fit a traditional relational design well.

2. Classification According to Number of Users

Single-User DBMS

A single-user DBMS is designed mainly for one user to access the database at a time.

Multi-User DBMS

A multi-user DBMS supports multiple users accessing the database concurrently. It requires mechanisms for concurrency control, security, and transaction coordination.

3. Classification According to Distribution

Centralized DBMS

A centralized DBMS manages a database located primarily at one central site.

Distributed DBMS

A Distributed Database Management System (DDBMS) manages a database whose data may be stored across multiple network-connected locations while attempting to provide coordinated database access.

4. Classification According to System Architecture

• Centralized architecture: major database processing occurs at a central system.
• Client/server architecture: clients request services from database servers.
• Multi-tier architecture: additional layers, such as an application server, are placed between users and the database.

These architectures build on the arrangements described in 1.11 Centralized and Client/Server Architectures for DBMSs.

5. Classification According to Purpose

General-Purpose DBMS

A general-purpose DBMS provides broad database capabilities that can be used by many different applications.

Special-Purpose DBMS

A special-purpose DBMS is designed or optimized for a narrower class of applications or data requirements.

Summary Comparison

Exam Questions

1. Mention any one difference between schemas and instances. (2025)
2. Illustrate and explain three-schema architecture. (2025)
3. Illustrate and explain two tier and three tier database application architecture. (2025)
4. Define Database Language. (2024)
5. Who is DBA? List the roles of DBA. (2024)
6. Explain any four types of Database user. (2024)
7. Define Data Model. (2023)
8. Why level of abstraction is maintained in database? (2023)
9. What are the types of database user? Explain each of them in brief. (2023)
10. Identify and explain different types of database languages with example. (2023)
11. Define data independence. (Model Q)
12. Explain three-schema architecture of database in detail. (Model Q)

Whole Chapter Summary

Database

A database is an organized collection of related data designed for efficient storage, retrieval, modification, and sharing. Relational databases commonly organize data through tables containing records and attributes.

Database Management System

A DBMS is the software layer that manages a database. It handles definition, retrieval, modification, security, integrity, concurrency, transactions, backup, and recovery.

Database Users and DBA

Database environments involve DBAs, designers, programmers, specialized users, and several categories of end users. The DBA has overall responsibility for administration, security, authorization, backup, recovery, and performance.

Benefits of Databases

Database systems help control redundancy, improve consistency, share information, enforce integrity, manage security, support concurrent users, and provide coordinated backup and recovery.

Data Models

A data model provides concepts for representing database structure, relationships, and constraints. Conceptual models represent real-world meaning, representational models describe implementable logical structures, and physical models describe storage details.

Schemas and Instances

The schema is the relatively stable structure of the database, while the instance is the actual data present at a specific time. Changing records changes the instance but does not necessarily change the schema.

Three-Schema Architecture and Data Abstraction

The architecture separates external user views, the overall conceptual structure, and internal physical storage. Mappings connect these levels, while abstraction hides irrelevant lower-level details.

Data Independence

Physical data independence allows internal storage changes without conceptual-schema changes. Logical data independence allows appropriate conceptual changes without forcing corresponding changes to external views.

Database Languages and Interfaces

DDL defines structures, DML modifies or retrieves data, DCL controls privileges, and TCL manages transactions. Users access these facilities through command-line, form, graphical, web, mobile, or programming interfaces.

Database System Environment

A complete database environment includes hardware, software, data, metadata, procedures, people, applications, and interfaces. These components work together to process and protect organizational information.

Centralized and Client/Server Architectures

Centralized architecture concentrates major database resources at one site. Two-tier systems connect clients directly to a database server, while three-tier systems place an application server between clients and the database.

Classification of DBMSs

DBMSs may be classified by data model, number of users, distribution, architecture, or purpose. One DBMS can belong to several categories because each classification describes a different property.

Last-Minute Revision Sheet