Relational Algebraic Operations for Incremental Materialized View Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Maintaining up-to-date materialized views in databases is costly and resource-intensive, as it often requires multiple scans and operations to identify and apply changes, impacting other database operations and performance.

Innovation Solution

Applying relational algebraic operations to generate a change result set that can be processed in a single pass, using operators like the provenance merge operator to update materialized views efficiently, reducing the need for multiple scans and optimizing the update process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional techniques are used to maintain materialized views, then the materialized views can be kept up-to-date, but the process is costly and resource-intensive with multiple scans and operations

Engineering Contradiction:
Improveup-to-date materialized viewsVSAvoiddatabase operation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the materialized view maintenance process into distinct operational phases: identifying changes in source tables, generating change result sets, and applying updates. This segmentation allows each phase to be optimized independently, reducing overall resource consumption while maintaining view freshness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-identifying changes in source tables before the actual materialized view update occurs. Change result sets are generated in advance, allowing the update process to proceed efficiently with prepared data, minimizing the impact on database operations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple scans and operations are performed to update materialized views, then completeness of updates is ensured, but the impact on other database operations increases

Engineering Contradiction:
Improvecompleteness of updatesVSAvoidupdate process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the change identification and update application processes from the main database operation flow. By separating change result set generation from the materialized view update process, the system ensures complete updates without requiring multiple scans of the entire database, thus reducing time loss.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Change result sets serve as an intermediary data structure between source tables and materialized views. This intermediary captures all necessary changes in a single pass, allowing complete updates to be applied efficiently without multiple database scans, thereby reducing the time impact on other operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If resource-intensive operations are used to maintain materialized views, then accuracy of view data is maintained, but overall database performance deteriorates

Engineering Contradiction:
Improveview data accuracyVSAvoiddatabase performance
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent implements a dynamic maintenance approach where the system adapts the update process based on change detection. By dynamically identifying only the necessary changes through change result sets and applying updates selectively, the system maintains view data accuracy while minimizing resource consumption and preserving database performance.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11256684B1Applying relational algebraic operations to change result sets of source tables to update a materialized view
Publication Date: 2022.02.22 AMAZON TECH INC
  • US11256684B1 patent drawing
  • US11256684B1 patent drawing
  • US11256684B1 patent drawing

AI summary

Algebraic operations are applied to change result sets for source tables to update a materialized view of a database incrementally. A procedure is determined for updating a materialized view that generates result sets for changes to source tables for a materialized view. The procedure performs one or more operations to update the materialized view using the result sets as operands in a relational algebra operator in the procedure to include the changes in the result sets in the materialized view.