When an application is built, an underlying data model is chosen to make that application effective. Frequently, other applications need the same data, only modeled differently.
The naïve solution of copying the underlying data and modeling is costly in terms of storage and makes data maintenance and evolution impossible. View mechanisms are a technique to model data differently for various applications without affecting the underlying format and structure of the data. The technique enables applications to customize shared data objects without affecting other applications that use the same objects. The growing data-manipulation needs of companies cannot be met by existing legacy systems that contain valuable data. Thus view mechanisms are becoming increasingly important as a way to model and use legacy data in new applications.Materialized views are views that have been computed and stored in databases. Because they reduce the need to recompute the view and/or data being queried, they speed up the querying of large amounts of data. Further,because they provide a systematic way to describe how to recompute the data, maintenance and evolution can be automated. Materialized views are especially useful in data warehousing, query optimization, integrity constraint maintenance, online analytical processing, and applications such as billing, banking, and retailing. This comprehensive volume, with a foreword by Jeff Ullman ofStanford University, will serve as a reference for students and commercial users, and encourage further use and development of materialized views.
| Foreword | ||
| Preface | ||
| Pt. I | Rejuvenation of Materialized Views | |
| 1 | Introduction to Views | |
| 2 | Maintenance Policies | |
| 3 | Applications of Materialized Views | |
| 4 | Challenges in Supporting Materialized Views | |
| Pt. II | Applications of Materialized Views | |
| 5 | Data Integration Using Self-Maintainable Views | |
| 6 | Using Object Matching and Materialization to Integrate Heterogeneous Databases | |
| 7 | Optimizing Queries with Materialized Views | |
| 8 | Answering Queries Using Views | |
| 9 | Adapting Materialized Views After Redefinition | |
| 10 | The Dynamic Homefinder: Evaluating Dynamic Queries in a Real-Estate Information Exploring System | |
| Pt. III | Maintenance of Materialized Views | |
| 11 | Maintenance of Materialized Views: Problems, Techniques, and Applications | |
| 12 | Incremental Maintenance of Recursive Views: A Survey | |
| 13 | Efficiently Updating Materialized Views | |
| 14 | Maintaining Views Incrementally | |
| 15 | Incremental Maintenance of Views with Duplicates | |
| 16 | Algorithms for Deferred View Maintenance | |
| 17 | Incremental Evaluation of Datalog Queries | |
| 18 | View Maintenance Issues for the Chronicle Data Model | |
| 19 | View Maintenance in a Warehousing Environment | |
| 20 | Efficient Maintenance of Materialized Mediated Views | |
| 21 | Updating Derived Relations: Detecting Irrelevant and Autonomously Computable Updates | |
| 22 | Queries Independent of Updates | |
| Pt. IV | Materialized Views and Olap | |
| 23 | Implementing Data Cubes Efficiently | |
| 24 | On the Computation of Multidimensional Aggregates | |
| 25 | Maintenance of Data Cubes and Summary Tables in a Warehouse | |
| Pt. V | Implementation and Performance Analysis of Materialized Views | |
| 26 | Oracle7 Snapshots | |
| 27 | Checking Integrity and Materializing Views by Update Propagation in the EKS System | |
| 28 | Deriving Production Rules for Incremental View Maintenance | |
| 29 | The Heraclitus DBPL with Application to Active Databases and Data Integration | |
| 30 | An Incremental Access Method of View Cache: Concept, Algorithms, and Cost Analysis | |
| 31 | A Performance Analysis of View Materialization Strategies[superscript 1] | |
| 32 | Join Index, Materialized View, and Hybrid-Hash Join: A Performance Analysis | |
| References | ||
| Source Notes | ||
| Contributors | ||
| Index |
Overview
When an application is built, an underlying data model is chosen to make that application effective. Frequently, other applications need the same data, only modeled differently.
The naïve solution of copying the underlying data and modeling is costly in terms of storage and makes data maintenance and evolution impossible. View mechanisms are a technique to model data differently for various applications without affecting the underlying format and structure of the data. The ...