Database System Table Change Tracking via Read-Only Triggers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems lack effective methods to track and analyze changes in database system tables while maintaining security and integrity, particularly in large-scale enterprise environments, where users need insights into evolving data without risking data corruption or loss.

Innovation Solution

A method and system that utilize risk-aware database system triggers with read-only access to monitor and audit changes in database system tables, creating a restricted proxy to dynamically track changes and generate insights based on substantive content, ensuring security and integrity through read-only event notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If users are granted access to database system tables to track and analyze changes, then users can gain insights into database evolution, but data security and integrity may be compromised due to potential data corruption or loss

Engineering Contradiction:
ImproveLoss of informationVSAvoiddata security and integrity
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent introduces a restricted proxy trigger as an intermediary component between users and database system tables. This proxy trigger captures change events and stores them in a separate audit table, allowing users to analyze database evolution without direct access to system tables. The intermediary structure enables information access while maintaining data security and integrity by preventing users from directly modifying system tables.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If a restricted proxy is created to dynamically track changes in database system tables, then change tracking capability is improved, but system complexity increases due to additional triggers and audit mechanisms

Engineering Contradiction:
Improvechange tracking capabilityVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the change tracking functionality into distinct components: (1) restricted proxy triggers that capture change events, (2) audit tables that store change data, and (3) view tables that present processed information to users. This segmentation allows precise change tracking while managing system complexity by organizing functions into modular, independently manageable units with clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If comprehensive monitoring of database system tables is implemented, then insights into database evolution are gained, but performance overhead increases due to continuous tracking and auditing

Engineering Contradiction:
Improveinsights into database evolutionVSAvoidperformance overhead
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent implements local quality by allowing users to create views that monitor specific columns or rows of interest rather than requiring comprehensive monitoring of entire system tables. The restricted proxy triggers can be configured to track only particular data elements relevant to user needs, reducing the overall monitoring burden and performance overhead while still providing valuable insights into database evolution for targeted areas.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11853282B2Gaining insights on database system table changes
Publication Date: 2023.12.26 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11853282B2 patent drawing
  • US11853282B2 patent drawing
  • US11853282B2 patent drawing

AI summary

Obtaining insights on how database system tables are evolving. In some instances, risk aware database system triggers that have read only access to the columns of interest are utilized, thereby allowing a user to fully study the changes made to the database system tables while maintaining the security and integrity of these database system tables. Additionally, these database system triggers can be used to audit changes that are happening on the database system tables using views.