Database Change Detection Using Sequence Columns

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database solutions require comprehensive comparisons of table data to detect changes, which is inefficient and resource-intensive, and anonymization methods apply static transformations that do not adapt to real-time data changes, compromising privacy guarantees.

Innovation Solution

Implementing a sequence column in tables to track changes by incrementing unique integer values for new entries, allowing for efficient change detection without analyzing data entries and applying real-time anonymization that adapts to data changes by recalculating and reapplying anonymization operations as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If comprehensive comparison of table data is performed to detect changes, then change detection accuracy is improved, but resource consumption and processing time increase

Engineering Contradiction:
Improvechange detection accuracyVSAvoidresource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential elements needed for change detection (row IDs and timestamps) from the complete table data, avoiding the need to compare all data entries. This selective extraction maintains change detection accuracy while significantly reducing resource consumption and processing requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the change detection process into two parts: (1) tracking metadata (row IDs and timestamps) maintained by the database system, and (2) comparison logic performed by the external system. This segmentation allows the database to handle data tracking efficiently while the external system focuses on change detection logic, reducing overall resource consumption.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If comprehensive comparison of table data is performed to detect changes, then change detection accuracy is improved, but processing time increases

Engineering Contradiction:
Improvechange detection accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent extracts only the essential elements needed for change detection (row IDs and timestamps) from the complete table data, avoiding the need to compare all data entries. This selective extraction maintains change detection accuracy while significantly reducing processing time.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary action by having the database system automatically maintain tracking metadata (row IDs and timestamps) as data changes occur. This pre-computed metadata is readily available for comparison, eliminating the need for time-consuming full data scans and enabling rapid change detection.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If static anonymization is applied during preprocessing, then privacy protection is improved, but adaptability to real-time data changes deteriorates

Engineering Contradiction:
Improveprivacy protectionVSAvoidadaptability to data changes
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent transforms static anonymization into a dynamic process by continuously monitoring data changes through row ID and timestamp tracking. When changes are detected, the anonymization process is automatically reapplied to the updated data, ensuring privacy protection adapts to real-time data changes while maintaining reliable privacy guarantees.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements feedback by using change detection results to trigger subsequent anonymization operations. The system continuously monitors for data changes and feeds this information back into the anonymization process, creating a closed-loop system that maintains privacy protection adaptability.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If real-time anonymization is implemented to adapt to data changes, then adaptability is improved, but computational overhead increases

Engineering Contradiction:
Improveadaptability to data changesVSAvoidcomputational overhead
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts and monitors only critical change indicators (row IDs and timestamps) rather than analyzing complete data sets for changes. This selective monitoring enables real-time adaptability while minimizing computational overhead by focusing only on essential change detection.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by performing anonymization only on the specific data portions that have changed, rather than re-anonymizing entire data sets. This approach maintains adaptability to data changes while significantly reducing computational overhead by limiting processing to necessary portions.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10901977B2Database independent detection of data changes
Publication Date: 2021.01.26 SAP SE
  • US10901977B2 patent drawing
  • US10901977B2 patent drawing
  • US10901977B2 patent drawing

AI summary

Techniques are described for identifying changes to databases. In one example, a table associated with a data set is identified containing at least one entry, each entry associated with a sequence column value. The sequence column value for new entries is automatically incremented by one from a last max value. At time T1, a total entry count and a maximum sequence column value of the entries is calculated and stored in metadata. At time T2 later than T1, a total entry count and a maximum sequence column value in the table is calculated and compared to the previously stored values. If the values are the same, the table has not changed; if the values are different, then a change has been made. In response to a determined change, the calculated total entry count and the maximum sequence column value at T2 is stored in the metadata.