Stage Database Data Loading for Payment Transaction Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for managing large volumes of transaction data in payment networks face inefficiencies due to the need to access and process substantial amounts of data, leading to increased time and potential errors, especially when dealing with flat files that lack structure for indexing and efficient access.

Innovation Solution

The system employs an access engine that loads data from backup databases into a stage database and then into a task database, utilizing indexing and data loaders to facilitate efficient data transfer and querying, leveraging technologies like the IBM DB2 Analytics Accelerator for improved data management and processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If data is stored in flat files without indexing structure, then data storage is simple, but data access time increases significantly

Engineering Contradiction:
Improvedata storage simplicityVSAvoiddata access time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating indexed data structures (star schema, fact tables, dimension tables) before data access operations. The IBM DB2 Analytics Accelerator pre-processes flat files into structured formats with indexes, enabling fast query execution without searching entire datasets.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary layer (IBM DB2 Analytics Accelerator) between the flat files and the query system. This intermediary pre-processes and structures the data into optimized formats, mediating between the simple storage of flat files and the fast access requirements of queries.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If substantial volumes of transaction data are accessed for multiple tasks, then comprehensive data availability is achieved, but processing time and error potential increase

Engineering Contradiction:
Improvedata availabilityVSAvoidprocessing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the substantial transaction data into organized data structures with fact tables containing transaction data and dimension tables containing contextual information. This segmentation allows selective access to specific data subsets for different tasks, reducing processing time while maintaining comprehensive data availability across multiple analytical operations.

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If data structures are enlarged to accommodate more transaction data, then data capacity increases, but access performance deteriorates

Engineering Contradiction:
Improvedata capacityVSAvoiddata access speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The patent transitions from one-dimensional flat file storage to multi-dimensional data structures including fact tables and dimension tables. This dimensional transformation enables efficient access to large volumes of data by organizing information hierarchically, allowing fast retrieval along different dimensional axes without linearly increasing access time with data volume.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11003648B2Systems and methods for use in loading data from backup databases to task databases
Publication Date: 2021.05.11 MASTERCARD INT INC
  • US11003648B2 patent drawing
  • US11003648B2 patent drawing
  • US11003648B2 patent drawing

AI summary

Systems and methods are provided for loading data from a database into a task database, via a stage database. One exemplary method includes accessing a backup database where the backup database includes multiple flat files and where each of the multiple flat files includes data and having a filename. The method also includes appending, by a computing device, the filename of one of the multiple flat files to an index stored in the computing device and changing a global variable associated with a data loader for the one of the multiple flat files to the filename. The method then further includes loading the data from the one of the multiple flat files into a stage database in memory of the computing device and transferring the loaded data in the stage database to a task database, thereby making the data available to queries associated with tasks relying on the loaded data.