Database Synchronization with Versioned Metadata

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Synchronization of databases with derived metadata that is not current with the raw data leads to inconsistencies, as stale metadata can be synchronized, causing databases to be in an inconsistent state, and existing solutions are resource-intensive and time-dependent.

Innovation Solution

A system and method that synchronizes raw data and metadata by assigning a version identifier to the raw data first, updating stale metadata to match the raw data's version identifier, allowing synchronization to occur at any time without regard to data staleness, and ensuring metadata remains fresh without requiring re-synchronization unless modified.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If synchronization is performed when metadata is stale, then synchronization can occur at any time, but the databases end up in an inconsistent state

Engineering Contradiction:

Improvesynchronization frequencyVSAvoiddata consistency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by updating stale metadata and assigning version identifiers before the synchronization process begins. This ensures that when synchronization occurs, the metadata is already current, preventing inconsistency while allowing synchronization at any time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses version identifiers as a feedback mechanism to track the state of raw data and metadata. By comparing version identifiers, the system can determine whether metadata is stale and requires updating before synchronization, ensuring consistency without restricting synchronization timing.

Inventive Principle:

Principle #23Feedback

2Reliability

If stale metadata is updated before synchronization, then metadata freshness is improved, but additional computing resources are consumed

Engineering Contradiction:

Improvemetadata freshnessVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies local quality by updating only the specific metadata that is stale rather than performing a complete database refresh. By identifying and updating only the affected metadata records with version identifiers, the system maintains freshness while minimizing computing resource consumption.

Inventive Principle:

Principle #3Local quality

3Reliability

If version identifiers are assigned to both raw data and metadata, then synchronization tracking is improved, but device complexity increases

Engineering Contradiction:

Improvesynchronization trackingVSAvoiddata structure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The version identifier serves multiple functions: it tracks the state of raw data, determines metadata freshness, and enables synchronization decisions. This multi-functionality improves synchronization tracking without proportionally increasing complexity, as the same identifier mechanism serves multiple purposes throughout the system.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7610317B2Synchronization with derived metadata

Publication Date: 2009.10.27 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A system and method for synchronizing a database comprising raw data and metadata derived from the raw data, but when the metadata has not yet been updated. The raw data and the metadata are first synchronized, with the raw data having been assigned a version number. After synchronization, any stale metadata will be updated and assigned the same version number as the raw data.