Snapshot isolation and integrity constraints in replicated databases Export

@article{citeulike:5828876, abstract = {Database replication is widely used for fault tolerance and performance. However, it requires replica control to keep data copies consistent despite updates. The traditional correctness criterion for the concurrent execution of transactions in a replicated database is 1-copy-serializability. It is based on serializability, the strongest isolation level in a nonreplicated system. In recent years, however, Snapshot Isolation (SI), a slightly weaker isolation level, has become popular in commercial database systems. There exist already several replica control protocols that provide SI in a replicated system. However, most of the correctness reasoning for these protocols has been rather informal. Additionally, most of the work so far ignores the issue of integrity constraints. In this article, we provide a formal definition of 1-copy-SI using and extending a well-established definition of SI in a nonreplicated system. Our definition considers integrity constraints in a way that conforms to the way integrity constraints are handled in commercial systems. We discuss a set of necessary and sufficient conditions for a replicated history to be producible under 1-copy-SI. This makes our formalism a convenient tool to prove the correctness of replica control algorithms.}, address = {New York, NY, USA}, author = {Lin, Yi and Kemme, Bettina and Peris, Ricardo J. and Marta Pati, {n}o-Mart'{i}nez and Jos\'{e} Enrique Armend\'{a}riz}, citeulike-article-id = {5828876}, citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=1538913}, citeulike-linkout-1 = {http://dx.doi.org/10.1145/1538909.1538913}, doi = {10.1145/1538909.1538913}, issn = {0362-5915}, journal = {ACM Trans. Database Syst.}, keywords = {1sr, acmtods, consistency, journal, replication, snapshot, snapshot-isolation}, number = {2}, pages = {1--49}, posted-at = {2009-09-23 10:45:29}, priority = {5}, publisher = {ACM}, title = {Snapshot isolation and integrity constraints in replicated databases}, url = {http://dx.doi.org/10.1145/1538909.1538913}, volume = {34}, year = {2009} }

TY - JOUR ID - citeulike:5828876 L3 - citeulike-article-id:5828876 N2 - Database replication is widely used for fault tolerance and performance. However, it requires replica control to keep data copies consistent despite updates. The traditional correctness criterion for the concurrent execution of transactions in a replicated database is 1-copy-serializability. It is based on serializability, the strongest isolation level in a nonreplicated system. In recent years, however, Snapshot Isolation (SI), a slightly weaker isolation level, has become popular in commercial database systems. There exist already several replica control protocols that provide SI in a replicated system. However, most of the correctness reasoning for these protocols has been rather informal. Additionally, most of the work so far ignores the issue of integrity constraints. In this article, we provide a formal definition of 1-copy-SI using and extending a well-established definition of SI in a nonreplicated system. Our definition considers integrity constraints in a way that conforms to the way integrity constraints are handled in commercial systems. We discuss a set of necessary and sufficient conditions for a replicated history to be producible under 1-copy-SI. This makes our formalism a convenient tool to prove the correctness of replica control algorithms. IS - 2 JF - ACM Trans. Database Syst. SN - 0362-5915 AD - New York, NY, USA EP - 49 TI - Snapshot isolation and integrity constraints in replicated databases PB - ACM VL - 34 SP - 1 KW - 1sr KW - acmtods KW - consistency KW - journal KW - replication KW - snapshot KW - snapshot-isolation AU - Lin, Yi AU - Kemme, Bettina AU - Peris, Ricardo AU - Marta Pati, {n}o-Mart'{i}nez AU - José Enrique Armendáriz PY - 2009/// UR - http://dx.doi.org/10.1145/1538909.1538913 ER -