Data Importer Flexible Order Referential Integrity

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional data import processes for sales lead generation require strict ordering of data tables to maintain referential integrity, making it complex and error-prone, especially when dealing with dependencies between records such as order lines, orders, and customers.

Innovation Solution

A two-stage data import process where records are initially accepted into an intermediate table without integrity checking, allowing for flexible import order, followed by moving 'clean' records to working tables once all related records are present, ensuring referential integrity without requiring a specific import order.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional data import processes are used with strict ordering requirements to maintain referential integrity, then data integrity is ensured, but the import process becomes complex and error-prone

Engineering Contradiction:

Improvereferential integrityVSAvoidimport process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data import process into two distinct phases: an initial import phase where data is loaded without strict ordering constraints, and a subsequent validation phase where referential integrity is verified. This segmentation allows the system to separate the complexity of integrity checking from the import operation itself, reducing import process complexity while maintaining reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary validation mechanism that acts as a mediator between the import process and referential integrity requirements. This intermediary layer validates relationships after data is imported, rather than enforcing strict ordering during import, thereby simplifying the import process while ensuring integrity through the intermediary validation step.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If strict ordering is enforced during data import to maintain referential integrity, then data integrity is maintained, but import efficiency decreases

Engineering Contradiction:

Improvereferential integrityVSAvoidimport efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary data import without integrity constraints, allowing all records to be loaded first. The referential integrity validation is then performed as a preliminary check before finalizing the import. This preliminary action approach enables bulk loading efficiency while maintaining reliability through subsequent validation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent maintains continuous import operations by allowing records to be processed in any order without interruption for integrity checks during the import phase. The useful action of data loading continues uninterrupted, and integrity validation is performed continuously after import completes, thereby maintaining productivity while ensuring reliability.

Inventive Principle:

Principle #20Continuity of useful action

3Reliability

If data tables are imported in a specific order to ensure referential integrity, then integrity is maintained, but the process becomes time-consuming

Engineering Contradiction:

Improvereferential integrityVSAvoidimport time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent inverts the conventional approach by not enforcing ordering during import. Instead of checking integrity during the import process in sequence, the system imports all data first and then validates relationships. This inversion eliminates time-consuming sequential checks during import, reducing import time while maintaining integrity through post-import validation.

Inventive Principle:

Principle #13The other way round (Inversion)

4Reliability

If referential integrity checking is performed during import, then data quality is ensured, but import flexibility is reduced

Engineering Contradiction:

Improvedata qualityVSAvoidimport order flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent extracts the referential integrity checking operation from the import process itself. By separating these two functions, the system allows flexible import ordering without integrity constraints during loading, then applies quality assurance through the extracted validation step. This extraction maintains data quality while restoring import flexibility.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS9773030B2Data importer for a sales prospector

Publication Date: 2017.09.26 ORACLE INT CORP

AI summary

A data importer for a sales prospecting system imports one or more data tables that each may include one or more records. The data importer first (a) imports a data table into an intermediate table. The data importer then (b) determines if the imported data table depends on another data table and moves one or more records from the imported data table that have no missing dependencies to a corresponding working table; and (c) determines a set of previously imported data tables that refer to the imported data table. The data importer then, for each previously imported data table, repeats (b) and (c) above.