Database Replication Request System for Account Object Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing account object metadata synchronization techniques are costly and time-consuming, as they require manual maintenance of database-related processes to ensure synchronization across different customer accounts, leading to inefficiencies and potential transactional inconsistencies.

Innovation Solution

The implementation of a replication request system that indicates a first account object, a source account, and target accounts, allowing for the determination of object dependencies and the replication of multiple account objects with point-in-time consistency, thereby simplifying data management and ensuring transactional consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual maintenance of database-related processes is used to ensure synchronization, then transactional consistency can be maintained, but the process becomes costly and time-consuming

Engineering Contradiction:
Improvetransactional consistencyVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements self-service through automatic dependency detection and replication execution. The replication request system automatically determines object dependencies and executes replication without manual intervention, eliminating the need for manual maintenance while preserving transactional consistency through automated point-in-time replication

Inventive Principle:
Principle #25Self-service

2Reliability

If manual maintenance of database-related processes is used to ensure synchronization, then transactional consistency can be maintained, but the process becomes costly

Engineering Contradiction:
Improvetransactional consistencyVSAvoidcomputational cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs self-service by automatically determining object dependencies and executing replication operations. This automation eliminates manual maintenance costs while maintaining transactional consistency through programmatic control of the replication process

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by determining object dependencies before execution and creating point-in-time snapshots. This advance preparation enables efficient replication execution and reduces computational costs during the actual synchronization process

Inventive Principle:
Principle #10Preliminary action

3Reliability

If replication of multiple account objects is performed with point-in-time consistency, then transactional consistency is ensured, but system complexity increases

Engineering Contradiction:
Improvetransactional consistencyVSAvoidreplication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary determination of object dependencies and creates point-in-time snapshots before replication execution. This advance preparation simplifies the replication process by pre-organizing the replication sequence and data state, reducing the apparent complexity during execution

Inventive Principle:
Principle #10Preliminary action

4Productivity

If automated replication system is implemented, then efficiency is improved, but manual control over synchronization processes is reduced

Engineering Contradiction:
Improvereplication efficiencyVSAvoidmanual control
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system implements feedback by providing interfaces that allow users to initiate replication requests and monitor replication status. This feedback mechanism maintains user control and visibility over the automated process, allowing manual initiation and oversight while benefiting from automated execution efficiency

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12314283B2Data object replication using database identification
Publication Date: 2025.05.27 SNOWFLAKE INC
  • US12314283B2 patent drawing
  • US12314283B2 patent drawing
  • US12314283B2 patent drawing

AI summary

A system for data object replication includes at least one hardware processor and at least one memory storing instructions. The instructions cause the at least one hardware processor to perform operations including parsing a replication request to obtain a data object and identification information identifying a set of databases at a first deployment of a data provider. A dependency of the data object to one or more additional data objects stored in the set of databases is detected. A sequential replication of the data object and the one or more additional data object from the first deployment to a second deployment of the data provider is performed. The second deployment is identified by the replication request. A sequence of the sequential replication is based on the detected dependency.