How deeply does 100 SQL Server Mistakes and How to Avoid Them cover atomicity?

Defines all-or-nothing behavior, demonstrates open-transaction failures, and defers broader transaction nuances to isolation and durability.

Atomicity

As explained in 100 SQL Server Mistakes and How to Avoid Them

Atomicity is the transaction property that makes all of a transaction's operations succeed or fail as one unit.

Atomicity makes every statement in a transaction commit or roll back as one logical unit. The statements either all succeed or all fail, protecting multi-step updates from partial completion. section 7.1 section 1.2.1

Mistake: assuming BEGIN TRANSACTION guarantees automatic cleanup after an error.

A stored procedure can leave a transaction open when an operation fails. Check SELECT @@TRANCOUNT; an unexpected value of 1 means the transaction still needs an explicit ROLLBACK. section 7.1
Use structured error handling, including TRY...CATCH and an explicit rollback path, so failures do not leave the transaction active. section 7.1

Sales-order insertion

InsertSalesOrder begins a transaction before inserting sales-order data. A valid execution completes the order; an invalid product ID raises a foreign-key error, showing why the procedure needs a rollback-aware error path.

How 100 SQL Server Mistakes and How to Avoid Them covers it

Cover of 100 SQL Server Mistakes and How to Avoid Them

liveBook manning.com

Read 100 SQL Server Mistakes and How to Avoid Them on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Learn Concurrent Programming with GoAn atomic operation is an indivisible operation that cannot be interrupted during its execution.
liveBook manning.com

API Design PatternsAtomicity is the property of treating a multi-step operation as an indivisible unit whose effects are either all applied or all undone.
liveBook manning.com

Think Distributed SystemsFailure atomicity is the property that an operation either completes as an indivisible unit or exposes no partial effect when execution fails.
liveBook manning.com

LatencyAtomicity is the transaction property that requires all of a transaction's operations to take effect or none of them to take effect.
liveBook manning.com

100 Java Mistakes and How to Avoid ThemAn atomic request is an operation that observes or updates its target as one indivisible action without an intervening state change.
liveBook manning.com

MongoDB 8.0 in Action, Third EditionAtomicity is a transaction property in which an operation completes entirely or has no effect.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellAtomicity is the property that a transaction's operations take effect as one indivisible unit.
liveBook manning.com

100 Go Mistakes and How to Avoid ThemAn atomic operation is an indivisible operation that cannot be interrupted by competing accesses to the same data.
liveBook manning.com

Advanced Algorithms and Data StructuresAn atomic operation is an operation that appears indivisible to concurrent observers, with no visible intermediate state.
liveBook manning.com

Data Pipelines with Apache Airflow, Second EditionAn atomic transaction is an indivisible database transaction whose operations either all take effect or have no effect.
liveBook manning.com

Grokking ConcurrencyAtomicity is the property that an operation occurs as one indivisible action, either completing entirely or not taking effect.
liveBook manning.com

Learn Rust in a Month of LunchesAn atomic operation is an indivisible computer operation that appears to other threads as either fully completed or not performed.

Compare how 13 books explain atomicity →

Related concepts

ACIDpart of · ACID is the set of database transaction properties—atomicity, consistency, isolation, and durability—that characterize reliable transactional behavior.
compare-and-exchange operationincludes · A compare-and-exchange operation atomically replaces a value with a desired value only if the current value matches an expected value.
read-modify-write operationincludes · An operation that reads a value from a location, computes or selects an update, and writes the resulting value back to that location.
atomic operationincludes · An atomic operation accesses or updates shared state as an indivisible action with respect to concurrent operations.
lockingalternative to · Locking is a synchronization technique that restricts concurrent access to shared resources or protected operations.
batchingimplemented by · Batching is the grouping of multiple data items, requests, or operations so they can be processed together as a unit.

This explainer was generated by Manning's knowledge graph from the text of 100 SQL Server Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.