Database Synchronization State Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems require multiple operations and complex logic to determine whether to insert or update a record, leading to inefficiencies and potential errors due to the lack of a single operation that can handle both scenarios effectively, and existing locking mechanisms can result in deadlocks and performance issues.

Innovation Solution

A synchronization operation is introduced that transforms a database from an unknown state to a known state using a single statement, which includes a SYNCHRONIZE keyword that allows for either inserting or updating a record based on its existence without prior knowledge of the state, and employs a one-step locking mechanism to prevent deadlocks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple operations (SELECT, INSERT, UPDATE) are used to determine and modify database state, then the database can be accurately updated or inserted, but the system complexity and execution time increase

Engineering Contradiction:
Improvedatabase state accuracyVSAvoidoperation sequence complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the SELECT, INSERT, and UPDATE operations into a single unified operation. The database system executes one atomic operation that automatically determines whether to insert or update based on the target record's existence, eliminating the need for separate operations and complex decision logic in application programs.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified database operation serves multiple functions: it can both insert new records and update existing records, and it can also determine the current database state. This single multi-functional operation replaces what previously required three separate operations (SELECT, INSERT, UPDATE) plus application-level decision logic.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If multiple operations are executed to ensure database state accuracy, then data integrity is maintained, but the execution time and system resources increase

Engineering Contradiction:
Improvedata integrityVSAvoiddatabase operation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By combining multiple operations into one atomic database operation, the patent eliminates the sequential execution overhead of SELECT followed by INSERT or UPDATE. The database system performs the state determination and modification in a single execution unit, significantly reducing the time required while maintaining data integrity through atomicity.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If traditional locking mechanisms are used between state determination and operation execution, then data consistency is ensured, but deadlocks may occur

Engineering Contradiction:
Improvedata consistencyVSAvoiddeadlock risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent eliminates the time window between state determination and operation execution by merging them into a single atomic operation. Since the entire process (state check + modification) occurs in one database execution unit without intermediate steps, traditional locking mechanisms are no longer needed, and the risk of deadlocks is eliminated while maintaining data consistency.

Inventive Principle:
Principle #5Merging (Combining)

4Reliability

If application programs implement decision logic to choose between INSERT and UPDATE, then the correct operation is selected, but the program complexity increases

Engineering Contradiction:
Improveoperation selection accuracyVSAvoidprogram logic complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The database system performs the decision-making function that previously required application program logic. The unified operation automatically determines whether to insert or update based on the target record's existence, making the system self-service the decision logic function. This eliminates complex if-else statements and decision trees from application code.

Inventive Principle:
Principle #25Self-service

5Reliability

If the database is accessed multiple times for state checking and modification, then accurate updates are achieved, but performance deteriorates

Engineering Contradiction:
Improveupdate accuracyVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent reduces database access from multiple separate operations (SELECT then INSERT/UPDATE) to a single unified operation. This single access point maintains update accuracy by atomically determining state and applying changes, while simultaneously improving system throughput by eliminating the overhead of multiple database round-trips and reducing lock contention.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS7707219B1System and method for transforming a database state
Publication Date: 2010.04.27 UNISYS CORP
  • US7707219B1 patent drawing
  • US7707219B1 patent drawing
  • US7707219B1 patent drawing

AI summary

A system and method for managing a database is provided. The system and method includes logic that supports an atomic synchronization operation initiated by execution of a single synchronization statement. This operation utilizes a single call to a database management system to transform a database table from a first unknown state to a known state that contains a specified target record containing one or more specified data values. The first unknown state may be a state that already contains the target record, or may instead be a state that does not contain the record. In the former instance, a record containing one or more of the data values is created, and in the latter instance, the existing record is updated. A one-step locking mechanism is performed in conjunction with the operation to prevent the occurrence of deadlock and to minimize the number of required lock requests.