Database Record Reference Generation via Hash Functions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database management systems face challenges in efficiently loading related data into data storages, often requiring sequenced data loads and increasing complexity due to the use of primary keys and foreign keys for relationships between tables.

Innovation Solution

A data management system that processes unprocessed data in multiple loads, allowing for independent loading of related data into tables by using column definitions to generate unique values for references, such as through hash functions, thereby breaking dependencies between tables.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If primary keys and foreign keys are used for relationships between tables, then data integrity and referential relationships are maintained, but data loading complexity increases and sequenced loading is required

Engineering Contradiction:
Improvedata integrityVSAvoiddata loading complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data loading process into independent loads that can execute in any sequence. Instead of requiring a single sequenced load that respects foreign key constraints, the system divides data loading into multiple independent operations, each capable of loading data into different tables without dependency on the order of execution.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism that decouples the relationship between tables during data loading. Rather than directly enforcing foreign key constraints that require sequenced loading, the system uses an intermediate layer that allows independent loading while maintaining referential integrity through alternative means such as deferred constraint checking or independent identifier generation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If primary keys and foreign keys are used for relationships between tables, then referential relationships are maintained, but computing time for queries increases

Engineering Contradiction:
Improvereferential relationshipsVSAvoidcomputing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the referential relationship enforcement from the data loading process itself. Instead of maintaining foreign key constraints that require continuous checking and sequencing during loading, the system separates the loading operation from the constraint enforcement, allowing faster independent loading while maintaining relationships through alternative mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary actions to establish data relationships before formal constraint enforcement. By pre-processing data to create independent identifiers and establishing relationships in advance through alternative means, the system reduces the computing time required during actual query operations while maintaining referential integrity.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If sequenced data loads are required, then data integrity is maintained, but productivity decreases

Engineering Contradiction:
Improvedata integrityVSAvoiddata loading efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces dynamic flexibility into the data loading process. Instead of a static, fixed sequence required by traditional foreign key constraints, the system enables dynamic loading orders where tables can be loaded in any sequence. The data integrity is maintained through dynamic mechanisms such as deferred constraint checking or independent identifier management that adapt to the loading order rather than requiring a predetermined sequence.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12242451B2Determining references to predefined types of records
Publication Date: 2025.03.04 SAP SE
  • US12242451B2 patent drawing
  • US12242451B2 patent drawing
  • US12242451B2 patent drawing

AI summary

Some embodiments provide a program that receives a set of data for a first record in a first table. The set of data comprises a set of values for a set of attributes. In a data loading process configured to load a subset of the set of data into a subset of a first set of columns in the first table, the program determines that a first column in a first set of columns does not belong in the subset of the first set of columns. The program generates the first record in the first table. The program generates a value for the first column in the first set of columns that refers to a second record in the second table configured to represent a defined type of record. The program stores the value in the first column in the first set of columns of the first record.