Enum Schema Embedding for SQL Code-Description Table Overhead

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current computing and storage architectures face significant processing overhead and power requirements when maintaining code-description tables and their relationships in relational databases, particularly during updates and data movement in and out of memory.

Innovation Solution

Converting code-description table data to an enumerated data type within a schema record, allowing for efficient data schema detection and migration, which includes identifying records referencing the code-description table and updating the schema to include relevant data elements, thereby reducing the need for maintaining table relationships and improving memory usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If code-description tables are used to store descriptive values in relational databases, then data organization and reference capability are improved, but processing overhead and power requirements increase significantly

Engineering Contradiction:

Improvedata organization and reference capabilityVSAvoidprocessing overhead and power requirements

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the code-description table data from the relational database structure and embeds it directly into the schema definition of records. This removes the need for separate code-description tables and their associated maintenance overhead, while preserving the data organization and reference capability through inline enumeration types.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent merges the code-description table data with the record schema by integrating enumeration types directly into the schema definition. This combination eliminates the separation between code tables and data tables, reducing the number of table relationships that need to be maintained while keeping the descriptive values accessible.

Inventive Principle:

Principle #5Merging (Combining)

2Quantity of substance

If code-description tables are maintained in relational databases, then descriptive data storage is improved, but processing overhead during updates and data movement increases

Engineering Contradiction:

Improvedescriptive data storageVSAvoidprocessing overhead during updates and data movement

Core Design Contradiction:

Quantity of substanceVSProductivity

Solution Approach 1:

The patent extracts code-description table maintenance operations from the database system. By embedding enumeration types directly in the schema, updates to descriptive data no longer require separate table update operations, data movements, or relationship maintenance, thereby reducing processing overhead during these operations.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary action by pre-defining enumeration types within the schema structure. This allows descriptive values to be established upfront in the schema definition, eliminating the need for ongoing maintenance operations during data updates and movements, thus improving productivity.

Inventive Principle:

Principle #10Preliminary action

3Ease of operation

If code-description tables are moved in and out of memory during host processing, then data accessibility is improved, but processing overhead and power consumption increase

Engineering Contradiction:

Improvedata accessibilityVSAvoidprocessing overhead and power consumption

Core Design Contradiction:

Ease of operationVSUse of energy by stationary object

Solution Approach 1:

The patent merges code-description data with the record schema structure, creating a unified representation that eliminates the need for separate memory movements. The enumeration types are embedded in the schema, allowing data accessibility without requiring repeated loading and unloading of code-description tables from memory during host processing operations.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent extracts the code-description table data from separate memory structures and integrates it into the schema definition. This eliminates the need for repeated memory movements of code-description tables during processing, reducing power consumption while maintaining data accessibility through the embedded enumeration types.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11892973B2Emulation of code-description tables on SQL databases using Enum data type

Publication Date: 2024.02.06 SANDISK TECHNOLOGIES LLC

AI summary

A method and apparatus for converting code-description table data to an enumerated data type in a schema record referencing the code-description table. A record of a table is identified that references the code-description table, and a portion of a schema describing the record is updated to include the relevant data of the code-description table as an enumerated type of the record schema. The enumerated type schema element includes data elements of the code-description table relevant to the record, each element having its own type. As additional records of the same table that are related to the code-description table are called, the enumerated type schema element may be updated to include additional code-description table data elements.