Database Change Mapping via Many-to-Many Tables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database comparison tools cannot effectively map the changes made to databases during software updates, making it difficult to identify the source of differences and optimize the upgrade process, which can lead to performance issues or data corruption.

Innovation Solution

A system and method that generate a many-to-many table (MTMT) to associate specific data or structural elements with the instructions from software updates, allowing for the identification of instructions that caused changes by comparing modified databases and their corresponding MTMTs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional database comparison tools are used, then database changes can be detected, but the source of changes cannot be identified

Engineering Contradiction:
Improvechange detection accuracyVSAvoidsource identification information
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent introduces an intermediary mapping table that stores the correspondence between database elements and software update instructions. This mapping table acts as a mediator between the database comparison results and the source instructions, enabling traceability of changes back to their originating update instructions without requiring direct analysis of the update code itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy of the mapping relationship between database elements and update instructions in a separate mapping table. This copied information structure allows the system to trace changes back to their sources by referencing the pre-established mappings, rather than needing to re-analyze the original update instructions.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If software updates are applied to databases, then new functionality is achieved, but performance issues and data corruption risks increase

Engineering Contradiction:
Improvesoftware update capabilityVSAvoiddatabase integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where database changes are tracked and mapped back to their source update instructions. This feedback loop enables verification of whether updates were applied correctly and allows for identification of problematic instructions that may have caused performance issues or data corruption, facilitating corrective actions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent establishes mapping relationships between database elements and update instructions before the actual updates are applied. This preliminary action creates a reference framework that enables post-update verification and troubleshooting, allowing the system to identify and potentially rollback problematic changes while maintaining overall system reliability.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If database updates are performed without mapping tools, then update speed is maintained, but troubleshooting efficiency decreases

Engineering Contradiction:
Improveupdate speedVSAvoidtroubleshooting time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs the mapping establishment as a preliminary action during the update process itself, rather than as a separate post-update analysis step. This allows the mapping information to be ready for immediate use during troubleshooting, eliminating the need for time-consuming reverse-engineering of update sources while maintaining update speed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10503727B2System and method for mapping database changes
Publication Date: 2019.12.10 SERVICENOW INC
  • US10503727B2 patent drawing
  • US10503727B2 patent drawing
  • US10503727B2 patent drawing

AI summary

Software updates that cause changes to a database accessible by software can be identified. A first database can be modified using first instructions associated with a first software update to generate a first modified database, and a second database can be modified using second instructions associated with a second software update to generate a second modified database. A difference between the first and second modified databases can be determined, and one or more instructions of the first or second instructions that caused the difference can be identified based on the difference. The first and second instructions can be converted into operations that, when performed against the first and second databases, result in first and second many-to-many tables being generated. The many-to-many tables can be queried to identify the operations associated with the difference between the first and second modified databases.