Abstract
Locking is a fundamental part of every relational database, or Relational Database Management System (RDBMS). SQL Server is based on the relational database model, and as such uses locking when data is accessed. Even though we frequently relate locking to performance problems, it plays a vital role in making sure your data is reliable during concurrent workloads. The way SQL Server, or any other RDBMS for that matter, takes care of this data reliability is by following the “ACID” properties, which were originally defined by Jim Gray in the 1970s but received their name in 1983 from Andreas Reuter and Theo Härder. These ACID properties are enforced upon single operations, which we know as transactions. The acronym ACID consists of four characteristics that guarantee data reliability inside transactions. The list below describes each of these characteristics.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Electronic Supplementary Material
Below is the link to the electronic supplementary material.
Rights and permissions
Copyright information
© 2015 Enrico van de Laar
About this chapter
Cite this chapter
van de Laar, E. (2015). Lock-Related Wait Types. In: Pro SQL Server Wait Statistics. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1139-7_7
Download citation
DOI: https://doi.org/10.1007/978-1-4842-1139-7_7
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-1140-3
Online ISBN: 978-1-4842-1139-7
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books