Partial Database Bootstrap for Source Deletion Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database bootstrapping methods require full reconstruction when deletions occur, which is resource-intensive and time-consuming, disrupting services and inefficiently managing data integrity.

Innovation Solution

A partial bootstrap process that identifies and deletes data keys in the destination database that are no longer present in the source database, allowing storage locations to be reused without requiring a full bootstrap.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a full bootstrap is performed to handle deletions in the source database, then data integrity is maintained, but processing resources and time are significantly increased

Engineering Contradiction:
Improvedata integrityVSAvoidbootstrap time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial action by performing only the necessary subset of bootstrap operations. Instead of executing a complete full bootstrap when deletions occur, the system identifies and processes only the specific data keys that were deleted from the source database. This selective approach maintains data integrity for affected records while avoiding the overhead of reprocessing entire datasets, thereby reducing bootstrap time and resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent segments the bootstrap process into distinct operational phases: identifying deleted data keys, selectively updating only affected destination database records, and skipping unchanged data. This segmentation allows the system to isolate and process only the minimal necessary changes rather than treating the entire database as a single unit requiring complete reconstruction, thus resolving the contradiction between maintaining integrity and reducing time loss.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a full bootstrap is performed to handle deletions in the source database, then data integrity is maintained, but service disruption increases

Engineering Contradiction:
Improvedata integrityVSAvoidservice availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements partial action by limiting the scope of bootstrap operations to only those data keys that were deleted from the source database. This selective processing approach maintains data integrity for affected records while minimizing service disruption, as the destination database remains operational for all non-affected data during the partial bootstrap process, thereby preserving service availability and productivity.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent applies local quality by treating different portions of the database differently based on their change status. Deleted data keys receive full bootstrap treatment to maintain integrity, while unchanged data keys skip the bootstrap process entirely and remain accessible. This localized approach ensures data integrity where needed while maintaining service availability for unaffected portions of the database.

Inventive Principle:
Principle #3Local quality

3Reliability

If a full bootstrap is performed to handle deletions in the source database, then data integrity is maintained, but processing resources are significantly increased

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by executing only the minimal necessary bootstrap operations for deleted data keys rather than performing a complete full bootstrap. This selective processing significantly reduces computing resources, memory usage, and energy consumption while still maintaining data integrity for the affected records, thereby resolving the contradiction between reliability and resource efficiency.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If traditional bootstrapping methods are used, then complete data synchronization is achieved, but efficiency is reduced due to unnecessary processing

Engineering Contradiction:
Improvedata synchronizationVSAvoidbootstrap efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements partial action by identifying and processing only the specific data keys that require synchronization updates. Instead of blindly reprocessing all data keys as in traditional methods, the system selectively applies bootstrap operations only to deleted keys, achieving complete data synchronization for affected records while eliminating unnecessary processing overhead, thus improving bootstrap efficiency without sacrificing synchronization completeness.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent employs feedback mechanisms by comparing the source database state with the destination database state to identify deleted data keys. This feedback-driven approach allows the system to dynamically determine which records require bootstrap processing, avoiding unnecessary operations on unchanged data and thereby improving efficiency while maintaining complete synchronization for records that actually need updating.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12585636B2Resource efficient partial bootstrap
Publication Date: 2026.03.24 INTUIT INC
  • US12585636B2 patent drawing
  • US12585636B2 patent drawing
  • US12585636B2 patent drawing

AI summary

Systems and methods are disclosed for a resource efficient partial bootstrap of one or more databases. Instead of the typical requirement of deleting all data from a destination database and performing a full bootstrap when deletions in data at a data source occurs, implementations herein disclose a resource efficient partial bootstrap process to identify deletions in data at the data source and update the destination database accordingly without requiring a full bootstrap. To perform partial bootstrapping, a system compares the set of data keys from a source index at the data source with the set of data keys from a destination index at the destination database to identify a difference between the two sets of data keys. The system then deletes the data keys in the destination index that do not appear in the source index (as identified in the difference between the two sets of data keys).