Smart Database Inflation via Production Data Mirroring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database inflation techniques are time and resource consuming, especially at early development stages, as they often rely on synthetic data or automation that records and replays user interface actions, which are not stable and inefficient for large-scale systems.

Innovation Solution

A system and method for smart database inflation that captures database activities triggered by specific business flows or transactions, processes this information to determine inflation rules and strategies, and inflates databases efficiently using a recorder, analyzer, and inflator components, eliminating the need for synthetic data and user interface instrumentation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If synthetic data or user interface recording/replay techniques are used for database inflation, then databases can be inflated with data, but the process is time and resource consuming

Engineering Contradiction:
Improvedatabase volumeVSAvoidinflation time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent creates mirror tables that copy the structure and data of production databases, then inflates these mirrors with realistic data patterns. This copying approach allows inflation to proceed in parallel without blocking production systems, significantly reducing inflation time while maintaining data realism.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary analysis of production database patterns, correlations, and data relationships before inflation begins. By pre-processing and storing these patterns in the mirror tables, the actual inflation process can proceed rapidly by applying pre-defined transformation rules rather than generating data from scratch.

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If user interface recording and replay automation is used, then database inflation can be automated, but it requires a stable user interface and system

Engineering Contradiction:
Improveinflation automationVSAvoidsystem stability requirement
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The patent extracts the essential data patterns, relationships, and correlation rules from production databases without requiring the user interface or application logic to be stable. By separating the data structure analysis from the application layer, the system achieves automation that is independent of UI stability, allowing inflation to proceed even when the system is still in development.

Inventive Principle:
Principle #2Taking out (Extraction)

3Manufacturing precision

If detailed user interface actions are recorded and replayed, then realistic operational data can be captured, but implementation complexity increases

Engineering Contradiction:
Improvedata realismVSAvoidinflation system complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

Instead of recording and replaying complex user interface actions, the system copies the essential data structures, relationships, and statistical patterns directly from production databases into mirror tables. This simplifies the inflation system by eliminating the need for UI instrumentation, action recording, and replay mechanisms, while still achieving high data realism through pattern-based generation.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10055297B1System, method, and computer program for smart database inflation
Publication Date: 2018.08.21 AMDOCS DEV LTD
  • US10055297B1 patent drawing
  • US10055297B1 patent drawing
  • US10055297B1 patent drawing

AI summary

A system, method, and computer program product are provided for smart database inflation. In use, a trigger signal to begin capturing information associated with database activities corresponding to one or more operational systems is detected. The trigger signal is triggered by a specific business flow or transaction in the one or more operational systems. In response to detecting the trigger signal, the information associated with the database activities corresponding to the one or more operational systems is captured for a duration of an event associated with the trigger signal. The information associated with the database activities includes valid operational data and one or more affected records associated with the one or more operational systems. Additionally, the information associated with the database activities corresponding to the one or more operational systems is duplicated in at least one mirroring table. Further, the information associated with the database activities corresponding to the one or more operational systems is processed to determine a nature of the information, a correlation of attributes associated with the information, and a configuration of inflation rules and inflation strategy. Moreover, the information associated with the database activities is processed to inflate one or more databases utilizing the information associated with the database activities in accordance with the inflation rules and inflation strategy.