1991
DOI: 10.1109/2.116888
|View full text |Cite
|
Sign up to set email alerts
|

Specifying interdatabase dependencies in a multidatabase environment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
27
0

Year Published

1995
1995
2003
2003

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 78 publications
(29 citation statements)
references
References 5 publications
0
27
0
Order By: Relevance
“…Dependences between data objects can generally be described by the tuple <S,D,P,C,A>, also known as D 3 (data dependency descriptor) [7]. S stands for the source objects and D for the destination objects.…”
Section: Specification Of Consistence Constraintsmentioning
confidence: 99%
“…Dependences between data objects can generally be described by the tuple <S,D,P,C,A>, also known as D 3 (data dependency descriptor) [7]. S stands for the source objects and D for the destination objects.…”
Section: Specification Of Consistence Constraintsmentioning
confidence: 99%
“…The issue of maintaining consistency of replicated data across loosely-coupled, semantically heterogeneous databases has been considered in, e.g., [9,10,27]. Our constraint checking problem can be seen as a special case (or first step) of that consistency maintenance problem.…”
Section: Related Workmentioning
confidence: 99%
“…The approach is similar to the simplest case in our family of protocols. Similar issues are addressed in [27], but no specific protocols are provided. In [10], an implementation mechanism based on active rules is proposed for maintaining replication consistency.…”
Section: Related Workmentioning
confidence: 99%
“…System reliability should also be significantly higher since there are fewer dependencies on network connectivity and the individual data sources (again, assuming that the system in which the materialized solution is stored is reliable). It is also less costly to implement any interdata source constraints that have been determined in the integration [2]. The disadvantages of a materialized solution include the initial cost of constructing the warehouse, and the cost of maintaining currency of the data.…”
Section: Introductionmentioning
confidence: 99%