{"id":3184,"date":"2025-07-07T14:01:21","date_gmt":"2025-07-07T14:01:21","guid":{"rendered":"https:\/\/diznr.com\/?p=3184"},"modified":"2025-07-07T14:01:21","modified_gmt":"2025-07-07T14:01:21","slug":"gate-cseit-database-transaction-in-database-with-introduction-basic","status":"publish","type":"post","link":"https:\/\/www.reilsolar.com\/pdf\/gate-cseit-database-transaction-in-database-with-introduction-basic\/","title":{"rendered":"GATE CSEIT\/Database\/ Transaction in Database ( With basic introduction)."},"content":{"rendered":"

GATE CSEIT\/Database\/. Transaction in Database ( With basic introduction).<\/p>\n

[fvplayer id=”290″]<\/p>\n

Transaction in Database Management System (DBMS)<\/strong><\/h3>\n

Introduction to Transactions<\/strong><\/h4>\n

A transaction<\/strong> in a Database Management System (DBMS) is a sequence of one or more database operations that are executed as a single logical unit of work. Transactions are used to maintain data integrity, consistency, and reliability<\/strong> in a database.<\/p>\n

For example, in a banking system, transferring money from one account to another involves multiple operations:<\/p>\n

    \n
  1. \n

    Deducting money from Account A.<\/p>\n<\/li>\n

  2. \n

    Adding money to Account B.<\/p>\n<\/li>\n<\/ol>\n

    If any of these operations fail, the entire transaction must be rolled back<\/strong> to maintain consistency.<\/p>\n

    Properties of Transactions (ACID Properties)<\/strong><\/h4>\n

    Transactions in a database follow ACID<\/strong> properties:<\/p>\n

      \n
    1. \n

      Atomicity<\/strong> \u2013 A transaction is either fully completed<\/strong> or fully rolled back<\/strong>.<\/p>\n<\/li>\n

    2. \n

      Consistency<\/strong> \u2013 The database remains in a valid state before and after the transaction.<\/p>\n<\/li>\n

    3. \n

      Isolation<\/strong> \u2013 Transactions are executed independently without interfering with each other.<\/p>\n<\/li>\n

    4. \n

      Durability<\/strong> \u2013 Once a transaction is committed, the changes are permanent<\/strong>, even if a system failure occurs.<\/p>\n<\/li>\n<\/ol>\n

      States of a Transaction<\/strong><\/h4>\n

      A transaction goes through different states during execution:<\/p>\n

        \n
      1. \n

        Active<\/strong> \u2013 The transaction starts execution.<\/p>\n<\/li>\n

      2. \n

        Partially Committed<\/strong> \u2013 All operations are performed, but changes are not yet saved.<\/p>\n<\/li>\n

      3. \n

        Committed<\/strong> \u2013 Changes are permanently stored in the database.<\/p>\n<\/li>\n

      4. \n

        Failed<\/strong> \u2013 Transaction execution is interrupted due to an error.<\/p>\n<\/li>\n

      5. \n

        Aborted<\/strong> \u2013 Transaction is rolled back to maintain consistency.<\/p>\n<\/li>\n<\/ol>\n

        Types of Transactions<\/strong><\/h4>\n
          \n
        1. \n

          Read-Only Transaction<\/strong> \u2013 Retrieves data without modifying it.<\/p>\n<\/li>\n

        2. \n

          Read-Write Transaction<\/strong> \u2013 Reads data, modifies it, and stores the changes.<\/p>\n<\/li>\n<\/ol>\n

          Transaction Control Commands in SQL<\/strong><\/h4>\n
            \n
          1. \n

            COMMIT<\/strong> \u2013 Saves all changes made by a transaction permanently.<\/p>\n<\/li>\n

          2. \n

            ROLLBACK<\/strong> \u2013 Undoes all changes made by a transaction.<\/p>\n<\/li>\n

          3. \n

            SAVEPOINT<\/strong> \u2013 Creates a checkpoint within a transaction to rollback to a specific point.<\/p>\n<\/li>\n

          4. \n

            SET TRANSACTION<\/strong> \u2013 Defines the properties of a transaction (e.g., isolation level).<\/p>\n<\/li>\n<\/ol>\n

            Conclusion<\/strong><\/h4>\n

            Transactions play a crucial role in maintaining database integrity and consistency<\/strong>. By following ACID<\/strong> properties and using transaction control commands, databases ensure that operations are reliable and error-free<\/strong>.<\/p>\n

            GATE CSEIT\/Database\/ Transaction in Database ( With basic introduction).<\/a><\/h3>\n

            Institute of Engineering Studies (IES, Bangalore)<\/a><\/h3>\n

            Database Management Systems Lecture Notes<\/a><\/h3>\n

            Chapter 17: Transactions<\/a><\/h3>\n

            Here\u2019s a simple and complete introduction<\/strong> to Transactions in Databases<\/strong>, ideal for GATE CSE\/IT<\/strong> preparation under the Database Management Systems (DBMS)<\/strong> subject.<\/p>\n

            \n

            \ud83d\udcd8 What is a Transaction in a Database?<\/strong><\/h2>\n

            \u2705 Definition<\/strong>:<\/h3>\n

            A transaction<\/strong> is a sequence of one or more SQL operations<\/strong> that perform a single logical unit of work in a database.<\/p>\n

            \n

            Example: Transferring money from Account A to Account B involves:<\/p>\n

              \n
            1. \n

              Deducting amount from A<\/p>\n<\/li>\n

            2. \n

              Adding amount to B
              \u2192 These two must happen together<\/strong> or not at all<\/strong> \u2014 that\u2019s a transaction<\/strong>.<\/p>\n<\/li>\n<\/ol>\n<\/blockquote>\n

              \n

              \ud83e\uddf1 Basic Properties of Transactions \u2013 ACID<\/strong><\/h2>\n
              \n
              \n\n\n\n\n\n\n\n\n
              Property<\/th>\nMeaning<\/th>\n<\/tr>\n<\/thead>\n
              A \u2013 Atomicity<\/strong><\/td>\nAll operations in a transaction are performed or none at all.<\/td>\n<\/tr>\n
              C \u2013 Consistency<\/strong><\/td>\nTransaction takes the database from one valid state to another.<\/td>\n<\/tr>\n
              I \u2013 Isolation<\/strong><\/td>\nConcurrent transactions should not interfere with each other.<\/td>\n<\/tr>\n
              D \u2013 Durability<\/strong><\/td>\nOnce committed, changes are permanent even if the system crashes.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
              \n
              <\/div>\n<\/div>\n<\/div>\n<\/div>\n
              \n

              \ud83d\udd04 Transaction States<\/strong><\/h2>\n
                \n
              1. \n

                Active<\/strong> \u2013 Transaction is being executed.<\/p>\n<\/li>\n

              2. \n

                Partially Committed<\/strong> \u2013 Last statement is executed.<\/p>\n<\/li>\n

              3. \n

                Committed<\/strong> \u2013 Changes are saved permanently.<\/p>\n<\/li>\n

              4. \n

                Failed<\/strong> \u2013 Some error occurred.<\/p>\n<\/li>\n

              5. \n

                Aborted<\/strong> \u2013 Changes are rolled back.<\/p>\n<\/li>\n<\/ol>\n

                \n

                \ud83e\uddea Example Transaction (SQL)<\/strong><\/h2>\n
                \n
                sql<\/div>\n
                \n
                \n