ACM Home Page
Please provide us with feedback. Feedback
Snapshot isolation and integrity constraints in replicated databases
Full text PdfPdf (743 KB)
Source
ACM Transactions on Database Systems (TODS) archive
Volume 34 ,  Issue 2  (June 2009) table of contents
Article No. 11  
Year of Publication: 2009
ISSN:0362-5915
Authors
Yi Lin  McGill University, Canada
Bettina Kemme  McGill University, Canada
Ricardo Jiménez-Peris  Universidad Politécnica de Madrid, Spain
Marta Patiño-Martínez  Universidad Politécnica de Madrid, Spain
José Enrique Armendáriz-Iñigo  Universidad Pública de Navarra, Spain
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 51,   Downloads (12 Months): 228,   Citation Count: 0
Additional Information:

appendices and supplements   abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1538909.1538913
What is a DOI?

APPENDICES and SUPPLEMENTS
Online appendix to snapshot isolation and integrity constraints in replicated databases. The appendix supports the information on article 11.


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.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
 
4
 
5
ANSI X3.135-1992. 1992. American National Standard for Information Systems—Database Language- SQL.
6
7
 
8
9
10
11
12
 
13
14
 
15
 
16
 
17
18
 
19
 
20
21
22
 
23
Microsoft SQL Server 2005. 2007. SQL Server 2005 row versioning-based transaction isolation.
 
24
 
25
Oracle Corporation. 2007. Oracle 11g Release 1.
 
26
27
 
28
 
29
 
30
 
31
 
32
PostgreSQL. 2007. PostgreSQL, the world's most advanced open source database.
 
33
 
34
 
35
 
36

Collaborative Colleagues:
Yi Lin: colleagues
Bettina Kemme: colleagues
Ricardo Jiménez-Peris: colleagues
Marta Patiño-Martínez: colleagues
José Enrique Armendáriz-Iñigo: colleagues