• Title/Summary/Keyword: incremental view refresh

Search Result 5, Processing Time 0.019 seconds

Performance Evaluation of XML Materialized View Refresh (XML 실체뷰 갱신 기법의 성능 평가)

  • Sung, Ho-Sang;Moon, Chan-Ho;Kang, Hyung-Chul
    • The KIPS Transactions:PartD
    • /
    • v.10D no.3
    • /
    • pp.387-398
    • /
    • 2003
  • Materialized views have received much attention for query performance improvement. They need to be refreshed whenever their underlying data sources are updated. They could be recomputed from scratch or they could be incrementally refreshed by reflecting only those portions of updates that affect them. With emergence of XML as the standard for data exchange on the Web, active research is under way on effectively storing and retrieving XML documents. In this paper, we describe a performance study on the incremental refresh of XML materialized views for the case where XML documents are stored in a relational DBMS, and XML materialized views are maintained with incremental refresh. We describe implementation of a prototype XML storage system that supports XML materialized views and their incremental refresh, and report the performance results obtained with the implemented system through a detailed set of experiments on the incremental refresh of XML materialized views. The results show that the XML view maintenance with incremental refresh outperforms the ordinary view recomputation.

A Framework of XML Materialized Views Using Incremental Refresh (점진적 갱신에 기반을 둔 XML 형성뷰 관리 프레임워크)

  • Im, Jae-Guk;Gang, Hyeon-Cheol;Seo, Sang-Gu
    • The KIPS Transactions:PartD
    • /
    • v.8D no.4
    • /
    • pp.327-338
    • /
    • 2001
  • The view can provide the user an appropriate portion of the database through data integration and filtering. Views can be materialized for query performance improvement, and in that cse, their consistency needs to be maintained against the updates of the underlying data. They can be either recomputed or incrementally refreshed by reflecting the relevant updates. Since XML could represent the structural information of the documents, for the XML materialized views, new techniques that differ from the previous ones for incrementally refreshing the relational views are required. In this paper, we propose a framework of XML materialized view management where the XML view derived from the underlying XML documents are materialized and incrementally refreshed against the updates of the underlying documents.

  • PDF

A Framework of XML Materialized View Maintenance (XML 실체 뷰 관리 프레임워크)

  • 임재국;문찬호;김영성;강현철;서상구
    • Proceedings of the Korean Information Science Society Conference
    • /
    • 2000.10a
    • /
    • pp.243-245
    • /
    • 2000
  • W3C(World Wide Web Consortium)가 XML(eXtensible Markup Language)을 차세대 웹 문서 표준으로 제안하면서 많은 응용에서 XML을 사용하려는 다양한 연구가 진행되고 있다. 뷰는 이질적인(heterogeneous) 데이터의 통합 및 여과(filtering) 기능을 통해서 사용자가 요구하는 데이터를 제공한다. 뷰의 구현 기법 중에서 실체 뷰(materialized view)는 뷰의 내용을 직접 저장하는 기법으로서, 사용자의 질의에 빠른 응답시간을 제공할 수 있다. 그러나 실체 뷰는 하부 데이터베이스가 변경되었을 경우에 일관성을 유지해야 하는 오버헤드가 있다. XML은 문서의 구조정보를 나타낼 수 있으므로 기존의 관계 데이터베이스와 객체지향 데이터베이스 등에서 연구되었던 실체 뷰 관리 기법과는 다른 XML 실체 뷰 관리 기법이 요구된다. 본 논문에서는 XML 문서를 대상으로 XML 실체 뷰를 지원하고, 데이터베이스에 저장된 XML 문서가 수정되었을 경우에 XML 실체 뷰에 대해 점진적 갱신(incremental refresh)을 지원하는 XML 실체 뷰 관리 프레임워크(framework)를 제안하였다.

  • PDF

Techniques of XML Query Caching on the Web (웹에서의 XML 질의 캐쉬 기법)

  • Park, Dae-Sung;Kang, Hyun-Chul
    • The Journal of Society for e-Business Studies
    • /
    • v.11 no.1
    • /
    • pp.1-23
    • /
    • 2006
  • As data on the Web is more and more in XML due to proliferation of Web applications such as e-Commerce, it is strongly required to rapidly process XML queries. One of such techniques is XML query caching. For frequently submitted queries, their results could be cached in order to guarantee fast response for the same queries. In this paper, we propose techniques for XML query performance improvement whereby the set of node identifiers(NIS) for an XML query is cached. NIS is most commonly employed as a format of XML query result,, consisting of the identifiers of the XML elements that comprise the query result. With NIS, it is suitable to meet the Web applications data retrieval requirements because reconstruction and/or modification of query results and integration of multiple query results can be efficiently done. Incremental refresh of NIS against its source updates can also be efficiently done. When the query result is requested in XML, however, materialization of NIS is needed by retrieving the source XML elements through their identifiers. In this paper, we consider three different types of NISs. proposing the algorithms of their creation, materialization, and incremental refresh. All of them were implemented using an RDBMS. Through a detailed set of performance experiments, we showed the efficiency of the proposed XML query caching techniques.

  • PDF

XML Vicw Indexing (XML 뷰 인덱싱)

  • 김영성;강현철
    • Journal of KIISE:Databases
    • /
    • v.30 no.3
    • /
    • pp.252-272
    • /
    • 2003
  • The view mechanism provides users with appropriate portions of database through data filtering and integration. In the Web era where information proliferates, the view concept is also useful for XML, a future standard for data exchange on the Web. This paper proposes a method of implementing XML views called XML view indexing, whereby XML view xv is represented as an XML view index(XVI) which is a structure containing the identifiers of xv's underlying XML elements as well as the information on xv. Since XVI for xv stores just the identifiers of the XML elements but not the elements themselves, when a user requests to retrieve xv, its XVI should be materialized against xv's underlying XML documents. Also an efficient algorithm to incrementally maintain consistency of XVI given a update of xv's underlying XML documents is required. This paper proposes and implements data structures and algorithms for XML view indexing. The performance experiments on XML view indexing reveal that it outperforms view recomputation for repeated accesses to the view, and requires as much as about 30 times less storage space compared to XML view materialization though the latter takes less time for repeated accesses to the view due to no need of materialization.