2007 IEEE 23rd International Conference on Data Engineering 2007
DOI: 10.1109/icde.2007.367873
|View full text |Cite
|
Sign up to set email alerts
|

Exploiting Correlation and Parallelism of Materialized-View Recommendation for Distributed Data Warehouses

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(10 citation statements)
references
References 5 publications
0
9
0
Order By: Relevance
“…That is, the source updates are committed without any concern of how and when the view manager will incorporate them into the view. This causes problems which we called maintenance anomalies: View maintenance, view synchronization, and view adaptation [7]. View maintenance maintains the materialized view extent under source data updates.…”
Section: Materialized View Maintenancementioning
confidence: 99%
“…That is, the source updates are committed without any concern of how and when the view manager will incorporate them into the view. This causes problems which we called maintenance anomalies: View maintenance, view synchronization, and view adaptation [7]. View maintenance maintains the materialized view extent under source data updates.…”
Section: Materialized View Maintenancementioning
confidence: 99%
“…This seems to be the first paper to present an algorithm for this type of constraint. The problem of choosing which views to materialize has also been researched in federated databases: [16] analyzes which views to materialize in front-end databases, and [13] analyzes which views to materialize in back-end databases. A self-tuning algorithm for data placement in distributed databases is proposed by [15].…”
Section: Related Workmentioning
confidence: 99%
“…However, these approaches depend on monotonic cost models, while considering updates and distributed data results in non-monotonic models [4,11]. All existing approaches to derive MVs in distributed scenarios we are aware of make prohibitive restrictions in order to obtain monotonic cost models or reduce the complexity, e.g., no update costs [4,10,12,25] or only one querying node [10,11,12,13,16].…”
Section: Introductionmentioning
confidence: 99%
“…A hybrid approach between the warehouse and the federation approach is suggested in [19] as a way to obtain a more flexible and applicable architecture. The idea is to aggregate selected data from the component data warehouses as materialized views and cache them at a federation server to improve query performance; a set of materialized query tables are recommended for the benefits of load distribution and easy maintenance of aggregated data.…”
Section: Warehousing Approachesmentioning
confidence: 99%