View Self-Maintenance

In general, Self-Maintenance refers to views being maintained without using all the base data. There exists different notions of its exact meaning depending on how much information is avaiable. At minimum, the view update is performed at the integrated system by only knowing the particular base data update that has occurred, the view definitions and the materialied data. We will be describing the alternative notions in detail here.

• Questions
  • Given a view, is it self-maintainable?
  • If it is self-maintainable, how?
• Single-View Self-Maintenance
  does not consider the materialized views
• Multiple-View Self-Maintenance
  makes use of contents of the other materialized views to minimize base data access
• Updates as a whole
  i.e., batch updates; may make maintenance easier and more efficient
• Making views self-maintainable
  When the answer to the first question listed above is No, we can define and materialize a minimal set of auxiliary views to make the original non-maintainable view maintainable. Here, basically we are increasing the amount of information available at the integrated system level.