Automated Database Change Logging via Centralized Service Engine

Solution Overview

Problem

Current database systems lack a convenient mechanism for centrally recording and managing changes to database tables, requiring database programmers to implement redundant and time-consuming code for change log management in each application.

Innovation Solution

A system comprising an administration tool, table metadata, and a service engine that tracks changes to selected columns, processing user requests and adding operations to a history table before relaying them to the database management system, thereby eliminating the need for manual code implementation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database programmers implement change log management code in each application, then change tracking capability is achieved, but development time and code redundancy increase

Engineering Contradiction:

Improvechange tracking capabilityVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the change log management functionality from individual database applications and places it in a separate, standalone service. This service runs independently and handles all change logging operations centrally, eliminating the need for each application to implement its own logging code while maintaining complete change tracking capability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a universal change logging service that can serve multiple database applications simultaneously. This single service provides change tracking for all connected applications, replacing the need for each application to have its own dedicated logging implementation, thereby reducing development time and eliminating code redundancy.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If database programmers implement change log management code in each application, then change tracking capability is achieved, but code redundancy and maintenance complexity increase

Engineering Contradiction:

Improvechange tracking capabilityVSAvoidcode redundancy

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the change log management functionality from individual database applications and places it in a separate, standalone service. This service runs independently and handles all change logging operations centrally, eliminating the need for each application to implement its own logging code while maintaining complete change tracking capability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent merges the change logging functionality from multiple separate applications into a single centralized service. This consolidation eliminates code redundancy by having one shared logging implementation that serves all applications, while still providing comprehensive change tracking across the entire system.

Inventive Principle:

Principle #5Merging (Combining)

3Productivity

If a centralized service engine is implemented to track changes, then development efficiency is improved, but system architecture complexity increases

Engineering Contradiction:

Improvedevelopment efficiencyVSAvoidsystem architecture

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a centralized change logging service as an intermediary component between database applications and the database system. This mediator service handles all change logging operations, allowing applications to focus on their core functionality while the intermediary manages the complexity of change tracking centrally.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the change log management functionality from individual database applications and places it in a separate, standalone service. This service runs independently and handles all change logging operations centrally, eliminating the need for each application to implement its own logging code while maintaining complete change tracking capability.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS9892137B2Automating the logging of table changes in a database

Publication Date: 2018.02.13 KYNDRYL INC

AI summary

A system and method for logging changes to a database table comprises an administration tool, table metadata, a history table, and a service engine. The administration tool provides an interface through which a database administrator (DBA), database programmer, or other user can manage the table metadata and the history table, including the selection of columns within the table for which the system will track changes.