Transaction processing

Database transaction

A database transaction symbolizes a unit of work, performed within a database management system (or similar system) against a database, that is treated in a coherent and reliable way independent of other transactions. A transaction generally represents any change in a database. Transactions in a database environment have two main purposes: 1. * To provide reliable units of work that allow correct recovery from failures and keep a database consistent even in cases of system failure. For example: when execution prematurely and unexpectedly stops (completely or partially) in which case many operations upon a database remain uncompleted, with unclear status. 2. * To provide isolation between programs accessing a database concurrently. If this isolation is not provided, the programs' outcomes are possibly erroneous. In a database management system, a transaction is a single unit of logic or work, sometimes made up of multiple operations. Any logical calculation done in a consistent mode in a database is known as a transaction. One example is a transfer from one bank account to another: the complete transaction requires subtracting the amount to be transferred from one account and adding that same amount to the other. A database transaction, by definition, must be atomic (it must either be complete in its entirety or have no effect whatsoever), consistent (it must conform to existing constraints in the database), isolated (it must not affect other transactions) and durable (it must get written to persistent storage). Database practitioners often refer to these properties of database transactions using the acronym ACID. (Wikipedia).

Video thumbnail

Relational Databases (part 1 of 6)

The essential concepts of relational databases. Part of a larger series teaching programming. Visit codeschool.org

From playlist Relational Databases

Video thumbnail

Database Transactions, part 1: Introduction

Learn about what transactions are, why you want to use them, and the SQL commands used.

From playlist SQL Databases

Video thumbnail

Database Transactions (ACID)

This computer science lesson covers the principles of database transactions with some simple examples. The ACID properties of a typical database transaction are described including Atomic, Consistent, Isolated and Durable. This tutorial briefly introduces the code of a Transact SQL (T-SQ

From playlist Databases

Video thumbnail

Tree Indexing in DBMS

A #database #index is a data structure that improves the speed of data retrieval operations on a database table at the cost of additional writes and storage space to maintain the index data structure. Indexes are used to quickly locate data without having to search every row in a database

From playlist Database

Video thumbnail

SQL

What is the structure of an SQL query? What logical operators and wildcards can be used in such queries?

From playlist Database Systems

Video thumbnail

Relational Databases (part 5 of 6)

The essential concepts of relational databases. Part of a larger series teaching programming. Visit codeschool.org

From playlist Relational Databases

Video thumbnail

Transaction SQL Tutorial | SQL Commit and Rollback | ACID Property in SQL | Edureka

( PHP & MySQL with MVC Frameworks Certification Training - https://www.edureka.co/php-mysql-self-paced ) Watch Sample Class recording: http://www.edureka.co/php-mysql?utm_source=youtube&utm_medium=referral&utm_campaign=transaction-sql-php A transaction is the propagation of one or more

From playlist PHP & MySQL Tutorial Videos

Video thumbnail

Database Transactions, part 5: Scripting

See a "real" example of transactions: putting multiple database commands into a script and wrapping them in a transaction.

From playlist SQL Databases

Video thumbnail

Lecture 10: Cloud Replicated DB, Aurora

Lecture 10: Cloud Replicated DB, Aurora MIT 6.824: Distributed Systems (Spring 2020) https://pdos.csail.mit.edu/6.824/

From playlist MIT 6.824 Distributed Systems (Spring 2020)

Video thumbnail

RailsConf 2021: Scaling Rails API to Write-Heavy Traffic - Takumasa Ochi

Tens of millions of people can download and play the same game thanks to mobile app distribution platforms. Highly scalable and reliable API backends are critical to offering a good game experience. Notable characteristics here is not only the magnitude of the traffic but also the ratio of

From playlist RailsConf 2021

Video thumbnail

RailsConf 2018: Putting Rails in a corner: Understanding database isolation by Emil Ong

Putting Rails in a corner: Understanding database isolation by Emil Ong If you've ever had inconsistent data show up in your app even though you wrapped the relevant code in a transaction, you're not alone! Database isolation levels might be the solution... This talk will discuss what da

From playlist RailsConf 2018

Video thumbnail

Lecture 12: Distributed Transactions

Lecture 12: Distributed Transactions MIT 6.824: Distributed Systems (Spring 2020) https://pdos.csail.mit.edu/6.824/

From playlist MIT 6.824 Distributed Systems (Spring 2020)

Video thumbnail

Database Transactions, part 3: ACID and Isolation

Learn about ACID (Atomic, Consistent, Isolated, Durable). We focus on Isolation and see what happens when transactions overlap.

From playlist SQL Databases

Related pages

Binary large object | Distributed transaction | Serialization | Nested transaction | Concurrency control | Data integrity | Serializability | Compensating transaction | Consistency (database systems) | Atomicity (database systems) | Rollback (data management) | ACID | Durability (database systems) | Isolation (database systems) | Commit (data management)