Database Change Impact Analysis via Source Code Hierarchy

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Database administrators and developers face challenges in predicting the impact of proposed changes to database schemas on applications and artifacts that access them, as existing tools are disconnected and cannot accurately assess how these changes affect the application and its components.

Innovation Solution

A method and system that analyze source code to identify affected portions by proposed database changes, generating a hierarchy of references to allow users to access and understand the impact of changes, enabling better prediction of required changes and preventing unintended consequences.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If database schema changes are proposed using traditional disconnected tools, then database administrators can propose changes efficiently, but they cannot predict how the application and artifacts would be affected by the change

Engineering Contradiction:

Improveimpact prediction informationVSAvoidtool integration complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges previously disconnected database administration tools with application analysis tools into an integrated system. The impact analysis tool combines DDL statement processing capabilities with source code analysis capabilities, allowing simultaneous examination of both database schema changes and their effects on application code through a unified interface.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary impact analysis tool that acts as a bridge between database administrators and application developers. This intermediary system processes DDL statements, analyzes source code for affected artifacts, and provides comprehensive impact reports that connect database changes to application consequences without requiring direct integration between disparate tool ecosystems.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Measurement precision

If developers manually analyze source code to assess database change impact, then they can identify affected portions, but the process is time-consuming and error-prone

Engineering Contradiction:

Improveimpact assessment accuracyVSAvoidanalysis time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The impact analysis tool performs self-service by automatically analyzing source code to identify artifacts affected by database changes. The system autonomously parses source code, traces dependencies on database objects, and generates impact reports without requiring manual code review, thereby eliminating human error and significantly reducing analysis time.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual process of code analysis with an automated computational system. The impact analysis tool uses computer algorithms to parse source code, identify database object references, and determine affected artifacts, substituting human manual inspection with automated mechanical analysis that is both faster and more accurate.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Loss of information

If comprehensive source code analysis is performed to identify all affected portions, then complete impact information is obtained, but the complexity of analyzing and organizing references increases

Engineering Contradiction:

Improveimpact information completenessVSAvoidreference organization complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the complex analysis results into organized hierarchical groups based on artifact types (e.g., tables, views, procedures). The impact report divides affected source code references into categorized sections, making comprehensive information more manageable and easier to navigate by presenting it in a structured, segmented format rather than as an undifferentiated mass.

Inventive Principle:

Principle #1Segmentation

4Productivity

If database administrators proceed with schema changes without impact analysis, then changes can be implemented quickly, but unintended consequences and exposure of sensitive information may occur

Engineering Contradiction:

Improveschema change speedVSAvoidchange safety

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by performing impact analysis before database schema changes are executed. The system evaluates the consequences of proposed DDL statements in advance, identifying affected artifacts and potential issues before the actual change occurs, allowing administrators to make informed decisions and prevent unintended consequences while maintaining implementation speed.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS8499281B2Identifying impact of database changes on an application

Publication Date: 2013.07.30 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A technique is disclosed for identifying impact of database changes on an application. Given a proposed database change, affected source code is identified that is affected by the proposed database change. References to the affected source code are created and organized into a hierarchy. A user can ascertain the extent of the impact by viewing the hierarchy and by using the hierarchy to access and view the affected source code in a visually distinct manner.