Chapter 13. Maintaining Data Consistency: Transactions and Locks
SQL Server 2000 is designed to serve multiuser environments. If multiple users try to access the same data, SQL Server must protect the data to avoid conflicting requests from different processes. SQL Server uses transactions and locks to prevent concurrency problems, such as avoiding simultaneous modifications to the same data from different users.
This chapter teaches you the following:
Basic concepts about transactions
How to use Transact-SQL statements to manage transactions
How to understand the common concurrency problems and avoid them when they arise
How to apply the right transaction isolation level
Lock types available in SQL Server
How to detect and avoid deadlocks
Get Microsoft® SQL Server™ 2000 Programming by Example now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.