Transactions, Database Items, Read/Write Operations, and DBMS Buffers

 

Transactions, Database Items, Read/Write Operations, and DBMS Buffers

1. What is a Transaction?

A transaction is an executing program that performs a logical unit of work on a database.
It consists of one or more database operations.

Typical operations in a transaction include:

  • Insertion of new data

  • Deletion of existing data

  • Modification (Update) of data

  • Retrieval (Read) of data

These operations can be written:

  • Inside an application program, or

  • Interactively using SQL commands.

2. Transaction Boundaries

Transactions usually have explicit boundaries in programs:

BEGIN TRANSACTION
   Database operations
END TRANSACTION

All operations between these two statements are considered one transaction.

A single application program may contain multiple transactions, each separated by transaction boundaries.

3. Types of Transactions

Transactions are classified into two types:

TypeDescription
Read-only transactionOnly retrieves data; does not modify the database
Read-write transactionReads and updates the database

Example:

  • Checking account balance → Read-only

  • Transferring money between accounts → Read-write

4. Database Representation in Transaction Processing

To simplify transaction processing concepts, the database is modeled as:

A collection of named data items

Each data item represents a unit of data.

Granularity of Data Items

The size of a data item is called granularity.

A data item could be:

  • A disk block

  • A database record

  • A field/attribute value

Examples:

GranularityExample
Large    Entire disk block
Medium    One record
Small    One attribute value

Transaction processing works independently of granularity.

5. Basic Database Operations

Transactions access data using two fundamental operations.

1. read_item(X)

Reads the database item X into a program variable.

2. write_item(X)

Writes the value from the program variable X back to the database item X.

These two operations are the basic building blocks of transaction execution.

6. How read_item(X) Works

When a transaction executes:

read_item(X)

The DBMS performs the following steps:

  1. Find the disk block address containing item X.

  2. Copy that disk block into main memory buffer (if not already there).

  3. Copy X from the buffer to a program variable X.

So the flow is:

Disk → Main Memory Buffer → Program Variable

7. How write_item(X) Works

When executing:

write_item(X)

The following steps occur:

  1. Find the disk block containing X.

  2. Copy the disk block into a memory buffer.

  3. Copy the program variable X into the buffer.

  4. Write the updated buffer back to disk.

Flow:

Program Variable → Memory Buffer → Disk

Step 4 actually updates the database permanently.

8. DBMS Buffers and Buffer Management

The DBMS uses buffers in main memory to temporarily store disk blocks.

A buffer:

  • Holds one disk block

  • Acts as a temporary working area

Why Buffers Are Used

Buffers help to:

  • Reduce disk I/O operations

  • Improve performance

  • Allow faster transaction processing

9. Delayed Disk Writing

Sometimes the DBMS does not immediately write modified buffers to disk.

Reasons:

  • More updates may occur soon

  • Writing immediately may reduce performance

The recovery manager decides when the updated buffer should be written to disk.

10. Buffer Replacement Policy

Main memory has limited buffers.

When all buffers are full and a new disk block must be loaded, the DBMS must choose which buffer to replace.

Common policy:

LRU (Least Recently Used)

The buffer that was used least recently is replaced.

If the buffer being replaced was modified, it must first be written back to disk.

11. Read Set and Write Set

Each transaction has:

Read Set

The set of all items the transaction reads.

Write Set

The set of all items the transaction updates.

Example:

Transaction T1 reads and writes X and Y.

Read Set = {X, Y}
Write Set = {X, Y}

12. Why These Concepts Matter

When multiple transactions run concurrently, they may:

  • Access the same data items

  • Update the same values

Without control, this may lead to:

  • Incorrect results

  • Data inconsistency

Therefore, concurrency control and recovery mechanisms focus on managing:

  • read_item

  • write_item

operations safely.

13. Simple Conceptual Flow of Transaction Execution

Transaction
     ↓
Read/Write Operations
     ↓
DBMS Buffers (Main Memory)
     ↓
Disk Storage (Database)

Summary

Transactions interact with the database using read and write operations, while the DBMS buffers manage data movement between disk and memory to ensure efficient and correct execution of database operations.

Comments

Post a Comment

Popular posts from this blog

Database Management Systems DBMS PCCST402 Semester 4 KTU CS 2024 Scheme

 About Me Database Management Systems DBMS PCCST402 Scheme and Syllabus Model Question Paper - KTU BTech DBMS PCCST402 2024 Scheme Module-1 Introduction to DBMS Introduction to DBMS Example  Database Database System Vs Traditional File Processing Advantages of using DBMS Database System Concepts and Architecture Data Models, Schemas and Instances   Three schema architecture and Data Independence Database Languages and Interfaces Centralized and Client Server Architectures in DBMS Classification of Database Management Systems Conceptual Data Modeling and Database Design Conceptual Modeling and the Role of the ER Model in Database Design Entities and Attributes  Company Database Application - Example Entity Types, Entity Sets, Keys, and Value Sets in the ER Model Initial Conceptual Design of the COMPANY Database Relationship Types in the ER Model Relationship Degree, Role Names, and Recursive Relationships Constraints on Binary Relationship Types Attributes of Relation...
Read more

Data Models, Schemas and Instances

  Data Models, Schemas and Instances  1. Data Abstraction In databases, data abstraction means hiding the complex details of how data is stored and focusing only on what is important. Different users can view data at different levels of detail depending on their needs. 2. Data Models A data model is a collection of concepts used to describe the structure of a database. It defines: Data types Relationships among data Constraints on data Operations for accessing and updating data Data models help us understand and design databases without worrying about low-level storage details. Categories of Data Models a) High-level / Conceptual Data Models Close to how users think about data. Use concepts like entities , attributes , and relationships . Example: ER (Entity–Relationship) Model . b) Representational (Implementation) Data Models In between conceptual and physical models. Easy for users to understand but still close to how data is st...
Read more

Introduction to Database Management System -DBMS

Image
In today’s digital world, almost every application—from mobile banking and e-commerce to university portals and hospital systems—depends on the efficient storage, organization, and retrieval of data. As the amount of information generated by individuals and organizations continues to grow, managing this data in a structured and meaningful way becomes essential. This is where database systems play a central role. A database can be thought of as a well-organized collection of related data, designed so that it can be easily accessed, managed, and updated. But the database itself is only one component. To manage it effectively, we rely on a specialized software package known as a Database Management System (DBMS) . A DBMS provides a systematic and automated way to store large volumes of data, enforce rules for consistency and correctness, protect data from unauthorized access, and allow multiple users to work with the data simultaneously without conflicts. A database typically has three...
Read more