1998
DOI: 10.1109/69.687978
|View full text |Cite
|
Sign up to set email alerts
|

Techniques for update handling in the enhanced client-server DBMS

Abstract: The Client-Server computing paradigm has significantly influenced the way modern Database Management Systems are designed and built. In such systems, clients maintain data pages in their main-memory caches, originating from the server's database. The Enhanced Client-Server architecture takes advantage of all the available client resources, including their long-term memory. Clients can cache server data into their own disk units if these data are part of their operational spaces. However, when updates occur at … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2001
2001
2006
2006

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(4 citation statements)
references
References 38 publications
0
4
0
Order By: Relevance
“…We attempt to fill this gap by providing a stochastic model for content evolution, which allows a client to make judicious requests for current data. Other work in related areas (e.g., [3,5,10]) has considered various alternatives for pushing updated data from a server to a cache on the client side. Lazy replica-update policies using replication graphs have also been discussed in, for example, [4].…”
Section: Introductionmentioning
confidence: 99%
“…We attempt to fill this gap by providing a stochastic model for content evolution, which allows a client to make judicious requests for current data. Other work in related areas (e.g., [3,5,10]) has considered various alternatives for pushing updated data from a server to a cache on the client side. Lazy replica-update policies using replication graphs have also been discussed in, for example, [4].…”
Section: Introductionmentioning
confidence: 99%
“…The server can maintain (partial) information about the contents of the clients' cache or simply broadcast all changes. Updates have been studied for many other caching architectures (e.g., see Franklin [1996], Delis and Roussopoulos [1998], and Amiri et al [2003]); studying update performance for semantic caching is an interesting avenue for future work.…”
Section: General Query Processingmentioning
confidence: 99%
“…While the discussion in Ref. [21][22][23] ) have considered various alternatives for pushing updated data from a server to cached data on the client side. In this framework, an update is ''pushed'' to a replication site whenever updated data exceeds a predetermined interval of values or whenever a query requires current data.…”
Section: Related Workmentioning
confidence: 99%