ACM Home Page
Please provide us with feedback. Feedback
Relaxed currency and consistency: how to say "good enough" in SQL
Full text PdfPdf (607 KB)
Source International Conference on Management of Data archive
Proceedings of the 2004 ACM SIGMOD international conference on Management of data table of contents
Paris, France
SESSION: Research sessions: consistency and availability table of contents
Pages: 815 - 826  
Year of Publication: 2004
ISBN:1-58113-859-8
Authors
Hongfei Guo  University of Wisconsin
Per-Åke Larson  Microsoft
Raghu Ramakrishnan  University of Wisconsin
Jonathan Goldstein  Microsoft
Sponsor
SIGMOD: ACM Special Interest Group on Management of Data
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 69,   Citation Count: 16
Additional Information:

abstract   references   cited by   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/1007568.1007661
What is a DOI?

ABSTRACT

Despite the widespread and growing use of asynchronous copies to improve scalability, performance and availability, this practice still lacks a firm semantic foundation. Applications are written with some understanding of which queries can use data that is not entirely current and which copies are "good enough"; however, there are neither explicit requirements nor guarantees. We propose to make this knowledge available to the DBMS through explicit currency and consistency (C&C) constraints in queries and develop techniques so the DBMS can guarantee that the constraints are satisfied. In this paper we describe our model for expressing C&C constraints, define their semantics, and propose SQL syntax. We explain how C&C constraints are enforced in MTCache, our prototype mid-tier database cache, including how constraints and replica update policies are elegantly integrated into the cost-based query optimizer. Consistency constraints are enforced at compile time while currency constraints are enforced at run time by dynamic plans that check the currency of each local replica before use and select sub-plans accordingly. This approach makes optimal use of the cache DBMS while at the same time guaranteeing that applications always get data that is "good enough" for their purpose.


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
{ABK+03} M. Altinel, C. Bornhövd, S. Krishnamurthy, C. Mohan, H. Pirahesh, and B. Reinwald. Cache Tables: Paving The Way For An Adaptive Database Cache. In VLDB, 2003.
3
 
4
 
5
{BR02} L. Bright and L. Raschid. Using Latency-Recency Profiles for Data Delivery on the Web. In Proc. In VLDB, 2002.
6
 
7
8
9
 
10
11
 
12
 
13
 
14
{LC02} S. Weissman L. and P. Chrysanthis. Personalizing Information Gathering For Mobile Database Clients. In SAC, 2002.
 
15
 
16
{LR03} A. Labrinidis and N. Roussopoulos. Balancing Performance And Data Freshness In Web Database Servers. In VLDB, 2003.
17
 
18
19
 
20
{RBSS02} U. Röhm, K. Böhm, H. Schek, and H. Schuldt. FAS - a Freshness-Sensitive Coordination Middleware for a Cluster of OLAP Components. In VLDB, 2002.
 
21
 
22
 
23
{SR90} A. Sheth and M. Rusinkiewicz. Management Of Interdependent Data: Specifying Dependency And Consistency Requirements. In Workshop on the Management of ReplicatedData, pages 133--136, 1990.
 
24
 
25
 
26

CITED BY  16
Collaborative Colleagues:
Hongfei Guo: colleagues
Per-Åke Larson: colleagues
Raghu Ramakrishnan: colleagues
Jonathan Goldstein: colleagues